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 p-ganssle
Recipients p-ganssle, xtreak
Date 2019-02-11.19:02:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
@Karthikeyan I would certainly consider this a duplicate of the encodings bug/behavior that you demonstrate. I don't see an existing bug on the tracker for it, though.

I think it's pretty clear that the interpreter needs to fail, but it seems to *crash* rather than exit gracefully with a non-zero return code, which I think is the main problem. I'll note that it *does* print some stuff out before it crashes, which makes me think that even though io and/or encodings hasn't loaded, you still are able to do the "print an error message" part of "print an error message and exit with non-zero error code".
Date User Action Args
2019-02-11 19:02:36p-gansslesetrecipients: + p-ganssle, xtreak
2019-02-11 19:02:34p-gansslesetmessageid: <>
2019-02-11 19:02:34p-gansslelinkissue35969 messages
2019-02-11 19:02:34p-gansslecreate