[Python-Dev] Python install layout and the PATH on win32 (Rationale part 2: Moving the python.exe) (original) (raw)
Paul Moore p.f.moore at gmail.com
Fri Mar 23 14:37:42 CET 2012
- Previous message: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 2: Moving the python.exe)
- Next message: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 2: Moving the python.exe)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 22 March 2012 23:15, VanL <van.lindberg at gmail.com> wrote:
Another use case was just pointed out to me: making things consistent with buildout. Given a similar use case (create repeatable cross platform environments), they create and use a 'bin' directory for executable files.
Another problem case: cx_Freeze. This currently breaks when installed in a viretualenv, as it locates the "Scripts" directory by appending "Scripts" to the directory of the python executable.
So the proposed change will break cx_Freeze. The Scripts->bin change will also break it.
Paul.
PS Yes, I need to report the existing bug. The point remains, however...
- Previous message: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 2: Moving the python.exe)
- Next message: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 2: Moving the python.exe)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]