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
    • Templates:
    • Story Points:
      0.3
    • Team:
      SQuaRE

      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

          Container Issues

            Activity

              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