-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-96670: Raise SyntaxError when parsing NULL bytes #97594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
97a8f83
to
cb89392
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's up with python3.12.abi.new having 22,644 additions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG except for one word in an error message, I think.
Wow, that's some error. Let me clean that up |
Signed-off-by: Pablo Galindo <[email protected]>
Ugh, force-push. :-( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see nothing else wrong, let's wait for Lysandros' LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as well!
I was going to ask "doesn't this break things for encodings where NULLs are normal, like UTF-16", but then realized we never supported that anyway: PEP 253: "It does not include encodings which use two or more bytes for all characters like e.g. UTF-16. The reason for this is to keep the encoding detection algorithm in the tokenizer simple." In that sense, we get a better error message for UTF-16 files with this PR than before. Prior, it would silently fail (behave as if an empty file), and with this PR:
|
Landing, thank you everyone for your great review and comments! And also thank @mdboom for checking the UTF-16, that was a good consideration :) P.S. Sorry for the force push :S |
…honGH-97594). (cherry picked from commit aab01e3) Co-authored-by: Pablo Galindo Salgado <[email protected]>
GH-104195 is a backport of this pull request to the 3.11 branch. |
Uh oh!
There was an error while loading. Please reload this page.