Author giampaolo.rodola
Recipients Gynvael.Coldwind, brian.curtin, carlfk, dsmiller, ezio.melotti, flox, fran.rogers, giampaolo.rodola, jaraco, loewis, mel, mhammond, michael.foord, nnorwitz, norvellspearman, r.david.murray, steve.dower, tim.golden, tim.peters
Date 2014-04-29.10:21:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398766897.45.0.482780376458.issue1284316@psf.upfronthosting.co.za>
In-reply-to
Content
If on one hand I agree that Python being in C:\PythonXX is not optimal for all the reasons which have been mentioned so far, changing such an old established aspect of the interpreter would be too much disruptive as a change.
To say one, being that on Windows 'python' is not recognized as a command, some folks rely on it simply living in C:\Python** and make that assumption into their scripts (I did exactly this in psutil: https://code.google.com/p/psutil/source/browse/make.bat?name=release-2.1.0#23).

I agree with what Martin says here: http://bugs.python.org/issue1284316#msg26236.
We should let Python live in C\:PythonXX and just fix permissions during installation so that when the installation completes C:\PythonXX will not be writable by limited users. 
If this introduces a performance issue because the pyd files cannot be created afterwards then simply create pyd files as part of the installation process (this should be done if "install for all users" option is checked).
History
Date User Action Args
2014-04-29 10:21:37giampaolo.rodolasetrecipients: + giampaolo.rodola, tim.peters, loewis, mhammond, nnorwitz, jaraco, mel, dsmiller, norvellspearman, carlfk, tim.golden, ezio.melotti, r.david.murray, michael.foord, brian.curtin, flox, fran.rogers, Gynvael.Coldwind, steve.dower
2014-04-29 10:21:37giampaolo.rodolasetmessageid: <1398766897.45.0.482780376458.issue1284316@psf.upfronthosting.co.za>
2014-04-29 10:21:37giampaolo.rodolalinkissue1284316 messages
2014-04-29 10:21:36giampaolo.rodolacreate