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 Alecz
Recipients Alecz, JT.Johnson, Sworddragon, amaury.forgeotdarc, bill_sanjose, eric.araujo, eric.smith, jiri.kulik, loewis, mark.dickinson, pierrebourgault, tomzych, tonypdmtr
Date 2015-02-06.18:32:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I ran into this issue by doing the following steps, though I did not try to reproduce:

1 - install Python 3.4
2 - have windows Always Open .py files with Python
3 - install Python 2.7

Then I encountered issues where all .py scripts were opened with Python 2.7. After some unsuccessful attempts I decided to uninstall Python 2.7

4 - remove Python 2.7

At this point, I had to update the file associations because Windows could not find Python 2.7 anymore

5 - update file associations

The issue is obviously that in at least a few places in the registry, the ..\shell\open\command has a value of ..\python.exe "%1"

In my case it was under all roots:


I corrected only the one under HKEY_USERS by adding %* and it resolved the issue.
Date User Action Args
2015-02-06 18:32:56Aleczsetrecipients: + Alecz, loewis, amaury.forgeotdarc, mark.dickinson, eric.smith, eric.araujo, JT.Johnson, tomzych, Sworddragon, bill_sanjose, jiri.kulik, pierrebourgault, tonypdmtr
2015-02-06 18:32:56Aleczsetmessageid: <>
2015-02-06 18:32:55Aleczlinkissue7936 messages
2015-02-06 18:32:55Aleczcreate