Author jaraco
Recipients carlfk, dsmiller, jaraco, loewis, mel, nnorwitz, norvellspearman, tim.peters
Date 2008-06-24.12:52:07
SpamBayes Score 3.64425e-05
Marked as misclassified No
Message-id <1214311930.15.0.710734380321.issue1284316@psf.upfronthosting.co.za>
In-reply-to
Content
+1 on using "Program Files" by default.

In addition to the points mentioned above, there are other considerations.

In 64-bit platforms (Windows XP x64 and Vista 64-bit), programs are
segmented by their binary compatibility (C:\Program Files and C:\Program
Files (x86)).  Installing Python to the proper program directory helps
keep it organized as to it's binary compatibility.

Additionally, I often run several version of Python side-by-side, and
having these clutter my root directory is simply unacceptable.

I've been running Python from C:\Program Files for years, and I have
encountered problems, even including the recent setuptools bug, but for
the most part, these issues have been worked out.  I add C:\Program
Files\Python and c:\Program Files\Python\Scripts to my path, and things
work well.  I would think that since only a few issues remain, if Python
is moved to the standard location, any remaining issues can be ironed out.
History
Date User Action Args
2008-06-24 12:52:10jaracosetspambayes_score: 3.64425e-05 -> 3.64425e-05
recipients: + jaraco, tim.peters, loewis, nnorwitz, mel, dsmiller, norvellspearman, carlfk
2008-06-24 12:52:10jaracosetspambayes_score: 3.64425e-05 -> 3.64425e-05
messageid: <1214311930.15.0.710734380321.issue1284316@psf.upfronthosting.co.za>
2008-06-24 12:52:09jaracolinkissue1284316 messages
2008-06-24 12:52:07jaracocreate