➜

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 syeberman
Recipients barry, brett.cannon, eric.snow, ncoghlan, r.david.murray, syeberman
Date 2016-09-07.20:50:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473281440.99.0.641215602806.issue28007@psf.upfronthosting.co.za>
In-reply-to
Content 
Consider a process that is terminated while writing a large .pyc file.  Currently a user can only fix this by deleting the .pyc file, which requires knowing where to look.  A developer can be expected to know this, but the end user of their application certainly would not.

.pyc files are a cache.  When your cache is corrupted, you recreate it.
History
Date User Action Args
2016-09-07 20:50:41syebermansetrecipients: + syeberman, barry, brett.cannon, ncoghlan, r.david.murray, eric.snow
2016-09-07 20:50:40syebermansetmessageid: <1473281440.99.0.641215602806.issue28007@psf.upfronthosting.co.za>
2016-09-07 20:50:40syebermanlinkissue28007 messages
2016-09-07 20:50:40syebermancreate