Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-2993

Products must not depend on anaconda

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: webservcommon
    • Labels:
      None

      Description

      setupRequired(anaconda) should be removed from webservcommon.table.

      We want to keep the stack buildable with any python 2.7, and should not explicitly depend on anaconda.

        Attachments

          Issue Links

          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-2605 Package flask dependencies

          • Won't Fix
          is triggered by

          RFC - An issue whose primary purpose is to advertise an intent and allow stakeholders to comment. RFC-48 Add Python requests package as external dependency

          • Implemented
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-4918 rename anaconda package -> lsst-dm/legacy-anaconda

          • Done

          RFC - An issue whose primary purpose is to advertise an intent and allow stakeholders to comment. RFC-52 Packages should list all direct dependencies in their ups table files

          • Implemented

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-4347 dax_imgserv 2015_10.0 build error

          • Done

          RFC - An issue whose primary purpose is to advertise an intent and allow stakeholders to comment. RFC-50 Simplify distribution of common python modules

          • Withdrawn

            Activity

            Descending order - Click to sort in ascending order
            Hide
            Permalink
            jammes Fabrice Jammes added a comment -

            Hi Joshua Hoblitt,

            It's difficult to be sure that all "supported" distribution will provide correct version of our python deps, on the other hand, using eups might lead to use of deprecated and non supported deps. virtualenv might not be compliant with eups... So for now I'll stick with the current way we manage dependencies, but I think in production we'll need to use systems deps or at least up-to-date deps.

            Cheers,

            Show
            jammes Fabrice Jammes added a comment - Hi Joshua Hoblitt , It's difficult to be sure that all "supported" distribution will provide correct version of our python deps, on the other hand, using eups might lead to use of deprecated and non supported deps. virtualenv might not be compliant with eups... So for now I'll stick with the current way we manage dependencies, but I think in production we'll need to use systems deps or at least up-to-date deps. Cheers,
            Hide
            Permalink
            jhoblitt Joshua Hoblitt added a comment -

            merged

            Show
            jhoblitt Joshua Hoblitt added a comment - merged
            Hide
            Permalink
            jhoblitt Joshua Hoblitt added a comment -

            The requests product has been updated to 2.9.1 and added to repos.yaml. The PR has been updated to add requests as a dep and CI passes:

            https://ci.lsst.codes/job/qserv-os-matrix/3944/

            Show
            jhoblitt Joshua Hoblitt added a comment - The requests product has been updated to 2.9.1 and added to repos.yaml . The PR has been updated to add requests as a dep and CI passes: https://ci.lsst.codes/job/qserv-os-matrix/3944/
            Hide
            Permalink
            jhoblitt Joshua Hoblitt added a comment -

            @fritz requested on HC that the version of the requests package be updated and that it be added to the qserv eups table file in place of anaconda.

            Show
            jhoblitt Joshua Hoblitt added a comment - @fritz requested on HC that the version of the requests package be updated and that it be added to the qserv eups table file in place of anaconda.
            Hide
            Permalink
            jhoblitt Joshua Hoblitt added a comment - - edited

            My understanding from Frossie Economou is that qserv team is OK with considering requests a "system dep", in the context for qserv_distrib, is that correct?

            If so, there's a couple of different ways of fulfilling that. I suspect that eventually, the best course will be some sort of virtualenv-ish setup that makes it easy to add new python deps. In the mean time, I suggest adding something along the lines of apt-get install -qq -y python python-dev python-setuptools python-yaml python-requests python-sqlalchemy to the qserv docker files. Fabrice Jammes, do you have any thoughts on how python deps should be handled?

            Show
            jhoblitt Joshua Hoblitt added a comment - - edited My understanding from Frossie Economou is that qserv team is OK with considering requests a "system dep", in the context for qserv_distrib, is that correct? If so, there's a couple of different ways of fulfilling that. I suspect that eventually, the best course will be some sort of virtualenv-ish setup that makes it easy to add new python deps. In the mean time, I suggest adding something along the lines of apt-get install -qq -y python python-dev python-setuptools python-yaml python-requests python-sqlalchemy to the qserv docker files. Fabrice Jammes , do you have any thoughts on how python deps should be handled?
            11 older comments

              People

              Assignee:
              jhoblitt Joshua Hoblitt
              Reporter:
              mjuric Mario Juric
              Reviewers:
              Fritz Mueller
              Watchers:
              Brian Van Klaveren, Fabrice Jammes, Fritz Mueller, Jacek Becla, Joshua Hoblitt, Kian-Tat Lim, Mario Juric
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: