Repository navigation
Skip byte strings in extract_python instead of crashing - #1259
Open
bysiber wants to merge 1 commit into
Open
bysiber wants to merge 1 commit into
bysiber wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
When a byte string like _(b'foo') is encountered during message extraction, _parse_python_string would return the bytes object which then caused a TypeError in ''.join(buf). Byte strings are not valid translation strings anyway, so return None to skip them. Added a test to confirm byte strings are silently skipped while normal strings are still extracted correctly.
akx
requested changes
Apr 10, 2026
akx
left a comment
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
LGTM, tiny addition request!
Sorry, something went wrong.
Comment thread
babel/messages/extract.py
Comment on lines
+713
to
+714
| if isinstance(body.value, bytes): | ||
| return None # byte strings are not translatable |
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
Like for the f-string case below, let's add a note for our future selves that we could warn in this case.
Suggested change
| if isinstance(body.value, bytes): | |
| return None # byte strings are not translatable | |
| if isinstance(body.value, bytes): | |
| # TODO: we could raise an error or warning when this occurs | |
| return None # byte strings are not translatable |
Sorry, something went wrong.
This branch has not been deployed
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.
When pybabel extract encounters a byte string like _(b'foo'), _parse_python_string returns a bytes object which then causes ''.join(buf) to crash with TypeError: sequence item 0: expected str instance, bytes found.
Since byte strings are not valid translation strings (gettext uses normal strings internally), this just skips them by returning None from _parse_python_string when it encounters bytes.
Added a test that confirms byte strings are silently skipped while normal strings in the same file are still extracted correctly.
Fixes #1190