gh-143089: Fix ParamSpec docstring to use list syntax instead of tuple #143265
+2
−2
Conversation
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
…f tuple Type checkers (mypy and pyright) require ParamSpec defaults to use list syntax, not tuple syntax. Updated the docstring examples to use [int, str] instead of (int, str) to match the typing specification and avoid misleading users.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Contributor
|
There is already an open PR (#143179) with the same change as the one made in this PR. Please avoid this kind of unnecessary work in the future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Type checkers (mypy and pyright) require ParamSpec defaults to use list syntax, not tuple syntax. Updated the docstring examples to use [int, str] instead of (int, str) to match the typing specification and avoid misleading users.
ParamSpecshould show two examples with a list instead of a tuple #143089