Repository navigation
Avoid false metadata matches in strings - #2139
Open
jw9829 wants to merge 1 commit into
Open
jw9829 wants to merge 1 commit into
jw9829 wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
henryiii
force-pushed
the
recommend-inline-metadata-in-strings
branch
from
b7e4c9d to
4dcf6d3
Compare
October 29, 2026 13:40
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.
Show how adjacent string literals keep a # /// script line from being mistaken for metadata by a simple scanner.
Fixes #1835.
📚 Documentation preview 📚: https://python-packaging-user-guide--2139.org.readthedocs.build/en/2139/