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

Mark Hammond skippy.hammond at gmail.com
Sat Mar 17 06:28:57 CET 2012


On 17/03/2012 12:25 PM, Carl Meyer wrote:
> Hi Mark,
>
> On 03/16/2012 05:53 PM, Mark Hammond wrote:
>> * All executables and scripts go into the root of the Python install.
>> This directory is largely empty now - it is mainly a container for other
>> directories.  This would solve the problem of needing 2 directories on
>> the PATH and mean existing tools which locate the executable would work
>> fine.
>
> I hate to seem like I'm piling on now after panning your last brainstorm
> :-), but... this would be quite problematic for virtualenv users, many
> of whom do rely on the fact that the virtualenv "stuff" is confined to
> within a limited set of known subdirectories, and they can overlay a
> virtualenv and their own project code with just a few virtualenv
> directories vcs-ignored.
>
> I would prefer either the status quo or the proposed cross-platform
> harmonization.

Yeah, fair enough.  I should have indicated it was 1/2 tongue-in-cheek, 
but figured it worth throwing it out there anyway :)

OTOH, the part that wasn't tongue-in-cheek was the part that said "why 
not change the other platforms instead of windows" (then wait for the 
inevitable replies), then "so those same reasons apply to Windows too" - 
eg "fleets of torch wielding windows admins" :)

Breaking the few tools I'm concerned about vs asking Van etc to continue 
taking the pain he feels isn't going to mean the end of the world for 
any of us.  So given the stakes in this particular discussion aren't 
that high, I'll try and summarize the thread over the next few days (or 
someone can beat me to it if they prefer) and we can ask someone 
semi-impartial to make a decision.  I'd be happy to nominate MvL if he 
feels so inclined (even though I haven't asked him).

Cheers,

Mark


More information about the Python-Dev mailing list