Venv reasonable defaults: Single activator script, default name for venv, auto install from requirements.txt and auto upgrade-deps

Packaging
2

I’ve made my position on these topics known under https://github.com/pypa/virtualenv/issues/2007#issuecomment-724660278. TLDR:

  1. In the spirit of explicit is better than implicit this was reverted in virtualenv.
  2. is trivially solvable via ~/.virtualenv/venv (though questionable if a good idea)
  3. We don’t have a consensus.
  4. Long topic going in detail about it at discuss.python.org/t/how-should-virtualenv-behave-respective-of-seed-packages-e-g-pip-by-default/4146
  5. I’m not sure this is technologically doable. Though would like to be.
  6. I’m not sure this is technologically doable for the same reason as 5.
  7. Doable via virtualenv plugin.
  8. A venv is a reference to host python, containing many absolute paths generated during install (e.g. within console scripts). No one managed to come up with a backward-compatible solution to make them relocatable. This likely would need solution first in the interpreter, then in pip.
1 Like