➜
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.
Created on 2015-03-10 13:38 by paul.moore, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg237767 - (view) | Author: Paul Moore (paul.moore) *  |
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) * |
Date: 2015-08-11 18:15 | |
I haven't seen this at all, so until we see a repro of it, I'm closing. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:13 | admin | set | github: 67814 |
| 2015-08-11 18:15:27 | steve.dower | set | status: open -> closed resolution: works for me messages: + msg248420 |
| 2015-03-10 13:38:37 | paul.moore | create | |