Title: Windows per-user install of 3.5a2 doesn't associate .py files with the new launcher
Type: Stage:
Components: Installation, Windows Versions: Python 3.5
Status: closed Resolution: works for me
Dependencies: Superseder:
Assigned To: steve.dower Nosy List: paul.moore, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2015-03-10 13:38 by paul.moore, last changed 2015-08-11 18:15 by steve.dower. This issue is now closed.

Messages (2)
msg237767 - (view) Author: Paul Moore (paul.moore) * (Python committer) Date: 2015-03-10 13:38
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).
msg248420 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2015-08-11 18:15
I haven't seen this at all, so until we see a repro of it, I'm closing.
Date User Action Args
2015-08-11 18:15:27steve.dowersetstatus: open -> closed
resolution: works for me
messages: + msg248420
2015-03-10 13:38:37paul.moorecreate