Repository navigation
Conversation
…rable pythonGH-156158 rejected a NUL in complexstr() given a str, but the iterable path packed each item without that check, so the example from the issue still built and addstr() dropped every cell after the NUL.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GH-156158 rejects a NUL in
curses.complexstr()built from astr, but not from an iterable, socomplexstr([complexchar('\0'), complexchar('B')])from the issue still builds andaddstr()drops every cell after the NUL. This adds the same check tocurses_pack_cell(), which packs the items of an iterable, so a NUL item now raisesValueError: embedded null charactertoo.No NEWS entry: the cell API has not been released.