This suggestion is no different from environemnt activation scripts of anaconda/pyenv/virtualenv -- without the other benefits of virtualenv.StephanAt least for Windows users this would simplify the situation a bit."Python command prompt" submenu.easily have multiple versions of Python, each with their ownThat way, the installer still doesn't need to mess with global PATH and you canrun without further prefix.start cmd.exe with an appropriate PATH so that python and pip"Python command prompt", which willI.e., Install under the "Python 3.6" start menu an additionalCould we do something similar for Python?assorted environment variables set to the appropriate include/library directories.set to the appropriate compiler (32/64 bits or ARM cross-compiler), andunder its Start menu item, each of which starts a cmd.exe with appropriate PATHOne (smaller) suggestion on the PATH situation on Windows:I noticed that Visual C++ Build Tools installs a number of "Command prompts"
2017-11-06 23:53 GMT+01:00 Ivan Pozdeev via Python-ideas <python-ideas@python.org>:
On 07.11.2017 1:48, Chris Barker wrote:
You can't. Windows versions don't create versioned executables. Got bitten with this myself.On Mon, Nov 6, 2017 at 9:52 AM, Michel Desmoulin <desmoulinmichel@gmail.com> wrote:
I know and you still:
- have to use py -m on windows, python3 linux, python in virtualenv...
can't you use python3 -m pip install .....
everywhere?
...Maybe they should?
(This is python-ideas, after all ;-) )
-- Regards, Ivan
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/
-- Regards, Ivan