Re: [Python-Dev] New Windows installer for Python 3.5

2015-01-04 Thread Steve Dower
Chris Angelico wrote: > On Mon, Jan 5, 2015 at 9:56 AM, Steve Dower wrote: >> (Windows will always put per-user PATH entries at the end). The py.exe >> launcher handles this best, and the system version will always be found >> first. >> >> As for versions, 3.5 vs 3.6 should be distinguished expli

Re: [Python-Dev] New Windows installer for Python 3.5

2015-01-04 Thread Chris Angelico
On Mon, Jan 5, 2015 at 12:20 PM, Steve Dower wrote: > Unfortunately, Windows enforces the PATH ordering. It constructs the PATH > from two registry keys, one is the system-wide value (that requires > administrative privileges to modify) and it is followed by the user's value > (that does not re

Re: [Python-Dev] New Windows installer for Python 3.5

2015-01-04 Thread Glenn Linderman
On 1/4/2015 2:56 PM, Steve Dower wrote: Unfortunately, I'm fairly restricted on naming convention. For some reason Windows Installer requires CAB files to be 8.3 names, where some of the 8 are reserved, so the names are pretty meaningless. Least common denominator, I'm sure. But a pretty stupid

Re: [Python-Dev] New Windows installer for Python 3.5

2015-01-04 Thread Chris Angelico
On Mon, Jan 5, 2015 at 9:56 AM, Steve Dower wrote: > (Windows will always put per-user PATH entries at the end). The py.exe > launcher handles this best, and the system version will always be found first. > > As for versions, 3.5 vs 3.6 should be distinguished explicitly ("py -3.5" vs > "py -3.6

Re: [Python-Dev] New Windows installer for Python 3.5

2015-01-04 Thread Steve Dower
Thanks for all the comments. I've responded all at once, since I don't think any of the points raised are going to immediately turn into intense discussion. Feel free to trim the rest of the post if you want to respond to just one of the points. Donald Stufft wrote: > Does signing the .exe’s th

Re: [Python-Dev] New Windows installer for Python 3.5

2015-01-04 Thread Eric Fahlgren
I believe that the new default location addresses your first question: the 64-bit will install in c:/Program Files/Pythonxx and the 32-bit in c:/Program Files (x86)/Pythonxx (at least this has been my standard practice for several years). Eric On Jan 4, 2015 7:03 AM, "Paul Moore" wrote: > On 3 J

Re: [Python-Dev] New Windows installer for Python 3.5

2015-01-04 Thread Nick Coghlan
On 4 January 2015 at 22:01, Paul Moore wrote: > On 3 January 2015 at 23:34, Steve Dower wrote: > Also, how does the launcher py.exe fit into the picture? Is it still > installed into the Windows directory? What about for a user install? > Are Python scripts associated with the launcher, and if so

Re: [Python-Dev] New Windows installer for Python 3.5

2015-01-04 Thread Paul Moore
On 3 January 2015 at 23:34, Steve Dower wrote: > I've put together a short post showing where I've been taking the Windows > installer for Python 3.5, since I know there are interested people on this > list who will have valuable feedback. > > http://stevedower.id.au/blog/the-python-3-5-installe