| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
What is the pyright error? Since this is valid syntax, maybe it's something for pyright to fix instead? |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks! I agree this example is less confusing if the type alias definition passed as the string to ast.parse() is one that type checkers would accept if it were in user code
Sorry, something went wrong.
|
Thanks @diceroll123 for the PR, and @AlexWaygood for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, something went wrong.
|
Thanks @diceroll123 for the PR, and @AlexWaygood for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
|
Sorry, @diceroll123 and @AlexWaygood, I could not cleanly backport this to 3.12 due to a conflict. cherry_picker 7900a85019457c14e8c6abac532846bc9f26760d 3.12 |
Sorry, something went wrong.
…ythonGH-127955) Fix typo in ast docs: ParamSpec defaults (cherry picked from commit 7900a85) Co-authored-by: Steve C <diceroll123@gmail.com>
|
GH-127959 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
Oh, it's not relevant for 3.12 because ParamSpec defaults are new in 3.13 |
Sorry, something went wrong.
…ython#127955) Fix typo in ast docs: ParamSpec defaults
| Back | FazBrowse Home | New Git URL |
Fixes a syntactical typo. The syntax is valid and works fine at runtime, but I noticed that pyright was nitpicky about it.
📚 Documentation preview 📚: https://cpython-previews--127955.org.readthedocs.build/