A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-March/117860.html below:

[Python-Dev] Python install layout and the PATH on win32

[Python-Dev] Python install layout and the PATH on win32 [Python-Dev] Python install layout and the PATH on win32VanL van.lindberg at gmail.com
Tue Mar 20 23:00:07 CET 2012
On 3/20/2012 4:49 PM, Mark Hammond wrote:
>
> So I'm assuming that:
> * The executable (and DLL) are moved to a "bin" directory in an 
> installed Python.
> * distutils etc will change to install all "scripts" (or executables 
> generated from scripts) into that same directory.  IOW, "Scripts" 
> would die.
> * A virtual-env would have an almost identical layout to an installed 
> Python.

Yes. I would make your point #3 stronger - I would like a virtualenv to 
have an identical layout to an installed python, at least with reference 
to the names of directories and the location of binaries. The base 
directory would be the only difference.

Thanks,
Van
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4