Author steve.dower
Recipients lauer@wpi.edu, paul.moore, skrah, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-05-25.18:13:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464199984.52.0.984083730435.issue27054@psf.upfronthosting.co.za>
In-reply-to
Content
I suspect PYTHONHOME is the problem and not the installation method. There have been thousands of (presumably successful) installations of Python 3.5, and I expect most of them are just for the current user (as that's the default). If these were all failing for this reason, we'd have heard before now :)

There are likely to be some configurations that will cause the initial install to fail if you aren't running as an administrator, but that doesn't sound like the issue here.

Rogue installers that write to Python's registry keys (e.g. Anaconda) are more likely to cause problems here, as are those that globally set environment variables like PYTHONHOME/PYTHONPATH. If, like me, you install a lot of different bundles to figure out which is best, then some of these may be lingering around.

But I'm 99.99% certain that our installer is not at fault and there's nothing to fix here.
History
Date User Action Args
2016-05-25 18:13:04steve.dowersetrecipients: + steve.dower, paul.moore, vstinner, tim.golden, skrah, zach.ware, lauer@wpi.edu
2016-05-25 18:13:04steve.dowersetmessageid: <1464199984.52.0.984083730435.issue27054@psf.upfronthosting.co.za>
2016-05-25 18:13:04steve.dowerlinkissue27054 messages
2016-05-25 18:13:04steve.dowercreate