New submission from Paul Moore: 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). ---------- assignee: steve.dower components: Installation, Windows messages: 237767 nosy: pmoore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Windows per-user install of 3.5a2 doesn't associate .py files with the new launcher versions: Python 3.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23626> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
