Repository navigation
[pyupgrade] Clarify default encoding argument handling (UP012) - #27315
Merged
ntBre merged 6 commits intoAug 28, 2026
Merged
Conversation
ntBre
requested changes
Jul 29, 2026
ntBre
left a comment
Contributor
There was a problem hiding this comment.
Thanks, but I don't quite understand the changes here. The issue is labeled
documentation
If you're using AI, please make sure to follow our AI Policy, or your contributions will be closed.
pyupgrade] Clarify default encoding argument handling (UP012)
ntBre
enabled auto-merge (squash)
August 28, 2026 19:45
ntBre
disabled auto-merge
August 28, 2026 19:46
ntBre
enabled auto-merge (squash)
August 28, 2026 19:47
1 task
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.
Hi! This updates UP012 documentation to describe both supported cases: replacing ASCII literals with bytes literals and removing redundant explicit UTF-8 encoding arguments. It also handles the latter for general expressions such as
str(exc).encode("utf-8"), which the rule previously skipped.Fixes #26854