This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author fran.rogers
Recipients brian.curtin, carlfk, dsmiller, ezio.melotti, flox, fran.rogers, jaraco, loewis, mel, mhammond, michael.foord, nnorwitz, norvellspearman, r.david.murray, tim.peters
Date 2010-04-27.21:06:46
SpamBayes Score 1.3467027e-10
Marked as misclassified No
Message-id <1272402409.31.0.0991940483434.issue1284316@psf.upfronthosting.co.za>
In-reply-to
Content
I'd like to concur that Python should install to %ProgramFiles% by default. The root-directory default is particularly anomalous on 64-bit Windows, where you have separate 64- and 32-bit Program Files directories; if I have a Python installation in "C:\Python26", is it amd64 Python or x86 Python? If I want to install both (since many packages don't yet support amd64), which one should I install to \Python26 and which should I rename?

As mel's post above (2005-11-15 11:39) points out, installing to C:\ is comparable to installing to /python2.6 on a Unix box; it's nonstandard, inelegant, and prone to ACL problems like the one this bug was opened for. If convenience on the command line (for non-power-users unfamiliar with %Path%) is the concern, a better solution would be a checkbox in the installer to add the new Python to the system %Path%.
History
Date User Action Args
2010-04-27 21:06:49fran.rogerssetrecipients: + fran.rogers, tim.peters, loewis, mhammond, nnorwitz, jaraco, mel, dsmiller, norvellspearman, carlfk, ezio.melotti, r.david.murray, michael.foord, brian.curtin, flox
2010-04-27 21:06:49fran.rogerssetmessageid: <1272402409.31.0.0991940483434.issue1284316@psf.upfronthosting.co.za>
2010-04-27 21:06:47fran.rogerslinkissue1284316 messages
2010-04-27 21:06:47fran.rogerscreate