GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — gh-132941: Soft deprecate various typing classes by srittau · Pull Request #154480 · python/cpython Conversation
|
Documentation build overview
430 files changed ·
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Great stuff!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
@JelleZijlstra @AlexWaygood Sorry to bother you, but could one of you review and merge this. While I only have 2 PRs open at the moment against CPython, I'm a bit worried about hitting the new 3 PR limit. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
No need to worry, we'll add you to the exclusion list. :-) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Couldn't you have mentioned this after I strong-armed these two into merging this PR? 😇 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I guess I don't need to do anything here? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
A review and (potential) merge would still be welcome, but became a bit less pressing for me. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| * :class:`typing.Optional` in favor of the dedicated union syntax | ||
| (``X | None``) | ||
| * :class:`typing.NoReturn` in favor of :class:`typing.Never` | ||
| * :class:`typing.ForwardRef` in favor of :class:`annotationlib.ForwardRef` |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
These last two are actually just aliases. Perhaps it's clearer to mention them separately?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
What exactly do you have in mind? As a whole new top-level item, a new sub-list inside this item, or just change "The following typing-related classes are :term:soft deprecated:" to "The following typing-related classes and aliases ..."?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I was thinking of just having two lists.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I've done that, but it looks a bit weird to me to separate the aliases from the rest of the typing-related items.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
| See :pep:`585` and :ref:`types-genericalias`. | ||
|
|
||
| .. class:: List(list, MutableSequence[T]) | ||
| .. class:: List[T](list, MutableSequence[T]) |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Unrelated but presenting List as a subclass of list is somewhat confusing
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Indeed, but it's consistent with the other classes in this doc (e.g. Set[T](set, MutableSet[T])).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Co-authored-by: Jelle Zijlstra <[email protected]>
|
|
||
| * The following typing-related aliases are :term:`soft deprecated`: | ||
|
|
||
| * :class:`typing.NoReturn` in favor of :class:`typing.Never` |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Sorry NoReturn is not an alias, but types.UnionType is.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I've moved it. I think it would be cleanest to use sub-headers, i.e. one for "re module" and one for "Typing-related". And then use one bullet point per item. But I'm not sure if that's in the spirit of the document.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.