Why do you want to avoid having to re-install modules for each version/environment?
In the general case, a module version is compatible only with a subset of Python versions, due to API changes from Python version to Python version. You also want to let each project decide with which module version it wants to work, due to potential incompatibilities between module versions (it is no accident that pip freeze preserves installed module versions). On Thu, 2021-07-22 at 19:37 +0300, Shlomo Solomon wrote: > Omer Zak <w...@zak.co.il> wrote: > > The answer to your prayers is pyenv. > > It allows you to install multiple Python versions in parallel, and > > for > > each version you can maintain several virtualenvs. > > Dan Yasny <dya...@gmail.com> wrote: > > How about using virtualenv for alternative versions? > > Yes, I know about pyenv and virtualenv, but wouldn't I have to > re-install modules for each version/environment? That's what I'm > trying > to avoid. -- There is no IGLU Cabal. The Cabal that can be spoken of is not the true Cabal. My own blog is at https://tddpirate.zak.co.il/ My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at https://www.zak.co.il/spamwarning.html _______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
