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 paul.moore
Recipients D Gentry, paul.moore, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2017-08-09.12:10:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502280631.66.0.132082480684.issue31148@psf.upfronthosting.co.za>
In-reply-to
Content
To be clear, Steve *is* our main Windows developer, and specifically the person who developed the Windows installers we now use. They work perfectly for many people, including myself, so there certainly isn't a general issue with them. I myself routinely install Python with the new installers on Windows 7 x64 systems, so it's definitely something specific to your system.

Is your PC running a "corporate" build that might include security restrictions or other permission limitations that might be affecting the behaviour of the installer?

As a workaround, Python is installable using nuget, from https://www.nuget.org/packages/python. I don't know much myself about nuget, but basically "nuget install python" will create a local copy of Python in the current directory that you can use without needing to be installed.
History
Date User Action Args
2017-08-09 12:10:31paul.mooresetrecipients: + paul.moore, tim.golden, r.david.murray, zach.ware, steve.dower, D Gentry
2017-08-09 12:10:31paul.mooresetmessageid: <1502280631.66.0.132082480684.issue31148@psf.upfronthosting.co.za>
2017-08-09 12:10:31paul.moorelinkissue31148 messages
2017-08-09 12:10:31paul.moorecreate