➜

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 paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-03-10.13:38:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425994717.16.0.260924440644.issue23626@psf.upfronthosting.co.za>
In-reply-to
Content 
Installing Python 3.5a2 with the 64-bit Windows installer using a user-level install doesn't associate .py files with the new (3.5) version of the launcher.

I encountered this when there was an existing system install of Python 3.4, so .py files remained associated with that. I presume in the absence of a previous install there would have been no association at all (but I haven't tested that).
History
Date User Action Args
2015-03-10 13:38:37paul.mooresetrecipients: + paul.moore, tim.golden, zach.ware, steve.dower
2015-03-10 13:38:37paul.mooresetmessageid: <1425994717.16.0.260924440644.issue23626@psf.upfronthosting.co.za>
2015-03-10 13:38:37paul.moorelinkissue23626 messages
2015-03-10 13:38:36paul.moorecreate