Show HN: Virtualenv-mv – Move (rename) Python virtualenvs

Re:Show HN: Virtualenv-mv – Move (rename) Python virtualenvs by devnonymous on Sunday June 12, 2016 @07:47AM (#11887671)

  > package manager is built into import system.
  > Importing a package that's not in the user's
  > environment yet will lead to something like
  > pip install at script startup

Here's a nifty little recipe I came up with to do just this by exploiting the import hooks introduced in py3.4

  http://lonetwin.github.io/blog/html/2016/05/16/auto_install_missing_python_modules.html

[ Parent | on HN ]

Re:Show HN: Virtualenv-mv – Move (rename) Python virtualenvs by maweki on Sunday June 12, 2016 @09:30AM (#11888007)

Please don't do that. Provide a requirements-file with the appropriate dependencies and their versions to use with `pip install -r `

[ Parent | on HN ]