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

2012-03-14 Thread Terry Reedy
On 3/14/2012 11:22 AM, VanL wrote: On 3/13/2012 9:58 PM, Terry Reedy wrote: Given that we already repeat it, isn't it better to be consistent? But there is no repetition currently on Windows installations. I though you were just proposing to switch lib (lower-cased, and scripts renamed as

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

2012-03-14 Thread VanL
On 3/14/2012 1:32 AM, Mark Hammond wrote: As per comments later in the thread, I'm -1 on including python{py_version_short} in the lib directories for a number of reasons; one further reason not outlined is that it would potentially make running Python directly from a built tree difficult. For

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

2012-03-14 Thread VanL
On 3/14/2012 10:56 AM, Terry Reedy wrote: Are you talking about 'install for all users' versus 'install for this user only'? I have always done the former as I see no point to the latter on my machine, even if another family member has an account. Yes, but some people are on corporate machines

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

2012-03-14 Thread Terry Reedy
On 3/14/2012 12:10 PM, VanL wrote: On 3/14/2012 10:56 AM, Terry Reedy wrote: Are you talking about 'install for all users' versus 'install for this user only'? I have always done the former as I see no point to the latter on my machine, even if another family member has an account. Yes, but

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

2012-03-14 Thread Jim J. Jewett
In http://mail.python.org/pipermail/python-dev/2012-March/117617.html van.lindberg at gmail.com posted: As noted earlier in the thread, I also change my proposal to maintain the existing differences between system installs and user installs. [Wanted lower case, which should be irrelevant;

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

2012-03-14 Thread VanL
On 3/14/2012 5:39 PM, Mark Hammond wrote: Can you offer any examples of 3rd party tools which could unify code in this scheme, and particularly, where this scheme would cause them to have less code, not more? How about virtualenv: def path_locations(home_dir): Return the path locations for

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

2012-03-14 Thread Mark Hammond
[resending - original reply went only to Van] On 15/03/2012 10:15 AM, Lindberg, Van wrote: On 3/14/2012 5:39 PM, Mark Hammond wrote: Can you offer any examples of 3rd party tools which could unify code in this scheme, and particularly, where this scheme would cause them to have less code,

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

2012-03-13 Thread VanL
Following up on conversations at PyCon, I want to bring up one of my personal hobby horses for change in 3.3: Fix install layout on Windows, with a side order of making the PATH work better. Short version: 1) The layout for the python root directory for all platforms should be as follows:

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

2012-03-13 Thread Brian Curtin
On Tue, Mar 13, 2012 at 14:43, VanL van.lindb...@gmail.com wrote: Following up on conversations at PyCon, I want to bring up one of my personal hobby horses for change in 3.3: Fix install layout on Windows, with a side order of making the PATH work better. Short version: 1) The layout for

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

2012-03-13 Thread Terry Reedy
On 3/13/2012 3:43 PM, VanL wrote: Following up on conversations at PyCon, I want to bring up one of my personal hobby horses for change in 3.3: Fix install layout on Windows, with a side order of making the PATH work better. Short version: 1) The layout for the python root directory for all

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

2012-03-13 Thread VanL
On 3/13/2012 4:19 PM, Terry Reedy wrote: What is {base/userbase} actually on a typical machine? It is fixed or user choice? It is based upon user choice and on whether it is a system-wide install (base) or a single-user install (userbase). Typically, though, it is just where you installed

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

2012-03-13 Thread VanL
On 3/13/2012 3:11 PM, Brian Curtin wrote: I'm familiar with the scripts/bin change. I take it the rest of that stuff matches *nix? Text later on seems to support this, so I think I'm on board with it. Yes, that is correct. Martin and I spoke on Friday and at least the bin/ folder and Path

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

2012-03-13 Thread Martin v. Löwis
1) The layout for the python root directory for all platforms should be as follows: stdlib = {base/userbase}/lib/python{py_version_short} platstdlib = {base/userbase}/lib/python{py_version_short} purelib = {base/userbase}/lib/python{py_version_short}/site-packages platlib =

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

2012-03-13 Thread VanL
On Mar 13, 2012, at 8:37 PM, Martin v. Löwis mar...@v.loewis.de wrote: 1) The layout for the python root directory for all platforms should be as follows: stdlib = {base/userbase}/lib/python{py_version_short} platstdlib = {base/userbase}/lib/python{py_version_short} purelib =

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

2012-03-13 Thread Terry Reedy
On 3/13/2012 9:57 PM, VanL wrote: On Mar 13, 2012, at 8:37 PM, Martin v. Löwismar...@v.loewis.de wrote: 1) The layout for the python root directory for all platforms should be as follows: stdlib = {base/userbase}/lib/python{py_version_short} platstdlib =

<    1   2