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

Remove pyenv instructions from pipelines.lsst.io build instructions

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: dm_dev_guide
    • Labels:
      None

      Description

      Nate Lust reports that many people have issues using pyenv to install Documenteer if their personal environments have small idiosyncracies:

      somehow the pyenv kept getting created with the python binary from the default miniconda installation and not the one from the conda env, and so the site_packages were all messed up, and complained about missing modules, but then after deactivating it was not restoring back to the conda env variables (even though the conda env looked to be activated, with the ps1 line and all) So as far as paths seemed to show things were fine, but the venv was tied to the wrong binary and that somehow was persisting after the venv was deactivating

      Given that, it's probably best to not recommend creating a venv virtual environment for Documenteer (just delete that content from the instructions).

      The ultimate end game is to distribute documenteer and its whole dependency tree as part of the conda base environment created by newinstall/lsstsw.

        Attachments

          Activity

          Hide
          jsick Jonathan Sick added a comment -

          John Swinbank, could you take a look at this change to the documentation build instructions? Since it seems be at least costing the Princeton team a fair amount of time to get pyvenv to work, it seems that it's not worth it. Do you agree? I don't know what the UW team's experience has been.

          Show
          jsick Jonathan Sick added a comment - John Swinbank , could you take a look at this change to the documentation build instructions? Since it seems be at least costing the Princeton team a fair amount of time to get pyvenv to work, it seems that it's not worth it. Do you agree? I don't know what the UW team's experience has been.
          Hide
          swinbank John Swinbank added a comment -

          For what it's worth, I like the virtualenv approach, and I've not been aware of it causing problems for anybody at UW.

          However, if this is a widespread issue, I don't object to these changes. One minor comment on GitHub. Also, it occurs to me — is it worth mentioning how to do this on top of the lsst-dev shared stack? I guess (but haven't tested) that's a matter of adding a --user to the pip invocation, or similar.

          Show
          swinbank John Swinbank added a comment - For what it's worth, I like the virtualenv approach, and I've not been aware of it causing problems for anybody at UW. However, if this is a widespread issue, I don't object to these changes. One minor comment on GitHub. Also, it occurs to me — is it worth mentioning how to do this on top of the lsst-dev shared stack? I guess (but haven't tested) that's a matter of adding a --user to the pip invocation, or similar.
          Hide
          jsick Jonathan Sick added a comment -

          Thanks. I added a note on --user.

          Hopefully all this'll be moot soon with documenteer finding its way into the regular installatin.

          Show
          jsick Jonathan Sick added a comment - Thanks. I added a note on --user . Hopefully all this'll be moot soon with documenteer finding its way into the regular installatin.

            People

            • Assignee:
              jsick Jonathan Sick
              Reporter:
              jsick Jonathan Sick
              Reviewers:
              John Swinbank
              Watchers:
              John Swinbank, Jonathan Sick
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel