-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
PEP 604 (Unions with pipe character) tracker #4819
Comments
Not yet supported by PyCharm https://youtrack.jetbrains.com/issue/PY-44974 |
This is not yet supported by pytype. Opened google/pytype#785. |
Pyre already supports this. If I'm reading https://youtrack.jetbrains.com/issue/PY-44974 correctly, PyCharm already supports it enough for us to use it. That leaves only pytype. |
This is the #1 feature I'm waiting for. This means we can basically replace any |
I think this is ready to be tested. |
Reopening for now due to a fix for python/mypy#10901 not being released, yet. This means, we can't use this in type aliases. |
I think mypy can now be ticked off, with the release of 0.920? |
We should be done now :) |
We should replace remaining uses of |
I'm reopening this to track the remaining mypy bugs. |
What is/are the bug(s) left? Is it listed on mypy side? |
None left now (to my knowledge)! All the significant bugs are now fixed on mypy |
This issue is supposed to track when we can start to use the pipe character as union (PEP 604) in typeshed. Support is needed in released versions of:
type[T]
(orType[T]
) in a PEP 604 type alias mypy#12392Callable
in a PEP 604 type alias mypy#12393TypeAlias
with new union syntax (PEP 604) mypy#11098Callable
in a PEP 604 type alias in a stub file with--python-version=3.9
mypy#14158The text was updated successfully, but these errors were encountered: