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 neologix
Recipients brett.cannon, neologix, pitrou, vstinner
Date 2011-10-31.15:08:00
SpamBayes Score 4.7926396e-09
Marked as misclassified No
Message-id <1320073681.21.0.959123433038.issue13303@psf.upfronthosting.co.za>
In-reply-to
Content
Then we won't write the bytecode any more.
But it will be consistent.
The solution would be to create a random temporary file (with e.g. mkstemp()): in case of crash, we'll let dangling temporary files, but we'll be able to update the bytecode.
I'm note sure it's worth it (and it won't be easy since we're really restricted in what we're allowed to call).
History
Date User Action Args
2011-10-31 15:08:01neologixsetrecipients: + neologix, brett.cannon, pitrou, vstinner
2011-10-31 15:08:01neologixsetmessageid: <1320073681.21.0.959123433038.issue13303@psf.upfronthosting.co.za>
2011-10-31 15:08:00neologixlinkissue13303 messages
2011-10-31 15:08:00neologixcreate