➜

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 ncoghlan
Recipients Julian, brett.cannon, ezio.melotti, lennartyseboodt, ncoghlan, pitrou
Date 2011-12-04.03:59:13
SpamBayes Score 1.3351918e-05
Marked as misclassified No
Message-id <1322971154.37.0.679414006992.issue13523@psf.upfronthosting.co.za>
In-reply-to
Content 
In Python 3.2 and later, standalone .pyc files are no longer created as a side effect of import. Instead, cached files are stored in a __pycache__ subdirectory and ignored completely if the corresponding source file is no longer present. (Standalone .pyc files may still be created explicitly for sourceless Python distribution)

See PEP 3147 for details.

Warnings for accidental use of standalone .pyc files will not be added to earlier versions, since there is no way for Python to tell the difference between accidental and deliberate use.
History
Date User Action Args
2011-12-04 03:59:14ncoghlansetrecipients: + ncoghlan, brett.cannon, pitrou, ezio.melotti, Julian, lennartyseboodt
2011-12-04 03:59:14ncoghlansetmessageid: <1322971154.37.0.679414006992.issue13523@psf.upfronthosting.co.za>
2011-12-04 03:59:13ncoghlanlinkissue13523 messages
2011-12-04 03:59:13ncoghlancreate