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 kristjan.jonsson
Recipients barry, christian.heimes, kristjan.jonsson, pitrou, serhiy.storchaka, vstinner
Date 2013-10-11.12:31:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Anyway, whether or not Pyhon guarantees this and that wrt. "untrusted" is beside the point and offtopic, as Victor poitns out.

However:  We are, and have always been, careful to fail gracefully if we detect data corruption.  Never should the flipping of a bit on a file on the disk cause our program to crash.  It is fine when reading a corrupt file that an int(1) turns to int(2), or that we get an UnmarshalError when reading it, or that a "hello world" string turns to "hello $orld".  What is not good is if the reading of the corrupt string causes the interpreter to crash.

My knowledge of the new unicode internals is limited at best.  If you don't think, Antoine, that putting non-7-bit data into the supposedly 7 bit ascii unicode data can cause an actual crash, but at worst a corrupt string, then I'm quite happy, personally :)
Date User Action Args
2013-10-11 12:31:49kristjan.jonssonsetrecipients: + kristjan.jonsson, barry, pitrou, vstinner, christian.heimes, serhiy.storchaka
2013-10-11 12:31:48kristjan.jonssonsetmessageid: <>
2013-10-11 12:31:48kristjan.jonssonlinkissue19219 messages
2013-10-11 12:31:48kristjan.jonssoncreate