➜

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 pierrebourgault
Recipients JT.Johnson, Sworddragon, amaury.forgeotdarc, bill_sanjose, eric.araujo, eric.smith, jiri.kulik, loewis, mark.dickinson, pierrebourgault, tomzych
Date 2011-01-13.22:07:30
SpamBayes Score 0.0016444654
Marked as misclassified No
Message-id <1294956457.43.0.251433935906.issue7936@psf.upfronthosting.co.za>
In-reply-to
Content 
I had the same problem with another version of python on Windows 7.

We are using python 2.4.2 for production and it is installed in D:\Tools\Python. For experimentation purpose, I installed Python 2.7 in the usual location. It broke a few things and I uninstalled both python, and reinstalled only 2.4.2.

After that, using python 2.4.2, I got the problem described by this issue. None of my colleagues (who did not install Python 2.7) had the issue. 

The registry entry HKEY_CLASSES_ROOT\py_auto_file\shell\open\command was reading: D:\Tools\Python\python.exe "%1"

It was missing %*. I added it and my issue went away.
History
Date User Action Args
2011-01-13 22:07:37pierrebourgaultsetrecipients: + pierrebourgault, loewis, amaury.forgeotdarc, mark.dickinson, eric.smith, eric.araujo, JT.Johnson, tomzych, Sworddragon, bill_sanjose, jiri.kulik
2011-01-13 22:07:37pierrebourgaultsetmessageid: <1294956457.43.0.251433935906.issue7936@psf.upfronthosting.co.za>
2011-01-13 22:07:30pierrebourgaultlinkissue7936 messages
2011-01-13 22:07:30pierrebourgaultcreate