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 vstinner
Recipients brett.cannon, matrixise, serhiy.storchaka, vstinner, yselivanov
Date 2015-11-25.14:17:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1448461030.47.0.279490207527.issue25643@psf.upfronthosting.co.za>
In-reply-to
Content
"especially for issues with null byte"

I don't think that we should put to much energy in handling correctly NUL bytes. I see NUL bytes in code as bugs in the code, not in the Python parser. We *might* try to give warnings or better error messages to the user, that's all.
History
Date User Action Args
2015-11-25 14:17:10vstinnersetrecipients: + vstinner, brett.cannon, serhiy.storchaka, yselivanov, matrixise
2015-11-25 14:17:10vstinnersetmessageid: <1448461030.47.0.279490207527.issue25643@psf.upfronthosting.co.za>
2015-11-25 14:17:10vstinnerlinkissue25643 messages
2015-11-25 14:17:10vstinnercreate