-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use most recent Python Syntax in .pyi files #161
Comments
Yes, go ahead.
|
Ok, I will start working on it. |
#207 is merged now. |
I will. |
Can I suggest PEP 673's Presently Unfortunately the documentation just lists the return type as |
To avoid regression, we should use the plugin |
Should this issue be still opened? |
This one would be interesting.
This one would be cool to have. Is it a problem for you if the issue remains open? |
No, I just would like to know the current status and the future plan. |
I updated the initial comment. |
Ruff linter is now merged to the master branch. |
By solving this feature, I solved below item.
|
I think below item seems to have already been resolved by the ruff linter introduced.
How do you think about it? |
Does it check that the generated code passes the rules of flake8-pyi? |
This is introduced by d08d5c4. |
Close this issue because all tasks are done. |
In .pyi files, the most recent syntax of python can be used, as it is only used for static analysis.
Therefore, these changes can be made:
|
instead ofOptional
andUnion
(PEP 604) (Use modern Python 3.10 syntax #207)type
Parameter Syntax (PEP 695)list
,dict
, … instead oftyping.List
,typing.Dict
, … (PEP 585)collections.abc
(Replace deprecated aliases to ABCs in collections.abc #223)Self
(PEP 673)I could work on this, to familiarize myself with the codebase.
The text was updated successfully, but these errors were encountered: