-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
types.GenericAlias and types.Union have no documentation #85971
Comments
See title. For reference:
I can do a PR which would need backporting (is that the right word?) to 3.9 at least for |
Hi, Patrick! Yes! It would be great if you could open a PR to document those new types. The documentation of types.Union should go to master only, and the documentation of types.GenericAlias to both master and 3.9, so two PRs should me opened to address this issues separately. The backporting (yes! that's the word) to 3.9 will be (fingers-crossed) automatic thanks to Mariatta's https://github.com/python/miss-islington |
Sorry, I'd completely forgotten about doing a PR for this. Go ahead! |
Thanks Ken Ji! Are you planning more doc patches? |
@guido, you're welcome! I'm thinking of updating the temporary hyperlinks for GenericAlias/PEP 585 in Union, subscriptions and typing, I'll submit 2 separate PRs since subscription and typing require backporting. If I think of anything major, I'll open a separate bpo to keep track of it there. Thanks. |
Cool. Please add me to the nosy list of any issues you open. Also, if you're interesting helping out with the match statement, once the SC approves it, we'll need to add docs for that. See bpo-42128 for a possible plan. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: