On 24 September 2014 23:16, Mike Miller
Hi all,
ProgramFiles was the default in Python 1.X.
It has been a supported option for just shy of 15 years on 2.X... most if not all the bugs (setuptools) were fixed a decade ago, and right now thousands, if not millions of people are running it under Program Files right now. I can vouch for several thousand because a company I work for distributes Python and pip there for its customers all around the world w/o issue.
I've never once encountered a bug due to install to ProgramFiles, or heard of anyone who has, and have been using Python for everything since the year 2000. If any rare bugs happen to surface, they can likely be fixed or replaced with a line of code, or worked around by installing elsewhere.
Right, the problem I was thinking of was actually a transient one during the 3.4 pre-release cycle (the ensurepip integration initially didn't work properly when installing into Program Files). So consider that a switch to +1 from me. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia