On Tue, Mar 24, 2020 at 09:40:07AM +0000, Rhodri James <[email protected]>
wrote:
> I'm afraid the terseness of your answer didn't make it at all clear how
> creating venvs would solve Fred's problems. It still isn't obvious to me!
One doesn't create virtual environments every day; once a year may be.
And there are projects that help managing environments if there are many
(virtualenvwrapper and virtualenvwrapper-win).
One doesn't activate venvs to run every script; once a day usually, or
once for every new terminal. And there're projects that help running
scripts in venvs automatically (pipsi and pipx).
Once a venv is activated there is no need to remember different commands
-- it's always ``python`` and ``pip``. In all operating systems. It's
what the OP wants, right?
> --
> Rhodri James *-* Kynesim Ltd
Oleg.
--
Oleg Broytman https://phdru.name/ [email protected]
Programmers don't die, they just GOSUB without RETURN.
_______________________________________________
Python-ideas mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/K4ZBR6NR3FLUV2ZQKBQTXQLUUMSCAUXH/
Code of Conduct: http://python.org/psf/codeofconduct/
