➜

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 Steve.Thompson
Recipients Steve.Thompson
Date 2010-09-03.19:33:02
SpamBayes Score 9.890881e-09
Marked as misclassified No
Message-id <1283542384.36.0.244541121538.issue9761@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm running pythong 2.6.1 on Windows XP SP3.

On many occasions I have ran into cases where I've installed a new package via the package's setup.py (pylint, logilab-common, etc) and new .pyc files don't get generated when I attempt to run the tools/packages.  I'm not sure if this should be considered a package issue or an interpreter issue.  I'd like to see the interpreter regenerate the .pyc file as expected so my colleagues and I don't burn time on "broken" packages we know nothing about only to find out it was due to some stale .pyc files.  A quick fix would be to make the packages in question clean out their installation directories or regenerate all the pyc files manually.

How should this issue be handled?
History
Date User Action Args
2010-09-03 19:33:04Steve.Thompsonsetrecipients: + Steve.Thompson
2010-09-03 19:33:04Steve.Thompsonsetmessageid: <1283542384.36.0.244541121538.issue9761@psf.upfronthosting.co.za>
2010-09-03 19:33:03Steve.Thompsonlinkissue9761 messages
2010-09-03 19:33:02Steve.Thompsoncreate