RetroSearch Browse

Thu Feb 12 18:13:19 CET 2015 · http://mail.python.org/pipermail/python-dev/2015-February/138167.html

Am 12.02.2015 um 15:46 schrieb Paul Moore:
> On 12 February 2015 at 08:05, Thomas Heller <theller at ctypes.org> wrote:
>> Maybe I'm more or less alone with the way I work, but I don't like
>> python.exe on my PATH (and py.exe alloes me to do this).
>> I start python scripts from the command line either with 'script.py'
>> or 'py -3.4 script.py' or 'py -2.7 script.py'.
>
> This is how I worked for a long time after py.exe became available.
> But then I discovered virtualenv, and started using that, and needing
> to use 2 completely different command sets for "when I'm in a
> virtualenv" vs "when I'm not" became completely unusable.

I'm normally not using virtual environments, so my understanding might
be wrong.  Isn't it the case that in virtual envs you don't have these
problems at all?  The 'correct' python.exe is on the PATH as well as the
Scripts directory:  this is what activate.bat does.

Thomas

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2015-February/138167.html below:

[Python-Dev] PEP 370 - per-user scripts directory on Windows