| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Tests were copied from typing_extensions Co-authored-by: Pradeep Kumar Srinivasan <gohanpra@gmail.com>
There was a problem hiding this comment.
Thanks a lot for your work! 👍
Sorry, something went wrong.
|
Did you mean to push some changes? Doesn't look like our comments were addressed. |
Sorry, something went wrong.
Sorry my bad. |
Sorry, something went wrong.
There was a problem hiding this comment.
The runtime behavior LGTM. If Jelle and Nikita (and anyone else interested) are happy with the docs I'll merge. Personally I think the docs are very clear too.
Thank you for implementing this James!
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM! Thanks again! 🎉
Sorry, something went wrong.
There was a problem hiding this comment.
I personally still find the documentation a little sparse, and would love to see more of the stuff from PEP 673 included in the typing module documentation. (It was a really great PEP! Extremely clear and informative, really nicely written — kudos 😀)
Nonetheless, the documentation you've added here looks great, and more can always be added in future PRs.
Congrats on the PEP being accepted! I'm super excited to start using this feature :)
Sorry, something went wrong.
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
|
Should an entry be added to "What's New in Python 3.11"? |
Sorry, something went wrong.
Yes. |
Sorry, something went wrong.
|
Should that be done in this PR? I thought the what's new was collated manually later. I assume typing.reveal_type() and friends should also get what's new entries. |
Sorry, something went wrong.
What's New entries can be added at any time, and often are edited in a later stage. But there's absolutely no rule that says you can't add one at the same time you change the code! We've had a tradition of not requiring What's New for a few reasons: devs writing code aren't always good at writing docs, and vice versa; and sometimes What's New needs to be reorganized to make it more readable for users who want to quickly know what's changed. We especially want to avoid that What's New reads like a Changelog file -- we have the Misc/NEWS entries for that (those can still be edited but it rarely happens unless there are blatant errors, and the goal there is to be complete, just not as detailed as "git log" output). So it's up to you. |
Sorry, something went wrong.
|
Thanks Guido! For my function PRs, I'd rather add a single PR summarizing all of them in What's New once we have decided on each of the PRs. I'm also happy to add a What's New entry for PEP 673 in that case. So I think this PR is ready to merge. |
Sorry, something went wrong.
|
@gvanrossum I think this can be merged now; Alex, Nikita, and I approved it. I'll work on What's New for typing in 3.11 once my other PRs are resolved. |
Sorry, something went wrong.
|
Let's see how the tests fare (tip: when the tests aren't run because the PR submitter is new to the project, ask a core dev to run the tests). |
Sorry, something went wrong.
|
Everything is green here now. |
Sorry, something went wrong.
| This annotation is semantically equivalent to using a :class:`TypeVar` with ``bound=Foo`` as | ||
| both the return annotation and the annotation for the ``self`` parameter. |
There was a problem hiding this comment.
I wonder if instead of this complicated sentence we should just show the code (with a comment saying something like "don't do this, do the other thing").
Maybe also explain how this is similar and different than
class Foo:
def return_self(self) -> "Foo":
...
Sorry, something went wrong.
|
Thanks a lot for this @Gobot1234 and @pradeep90! And thanks Jelle for sponsoring. |
Sorry, something went wrong.
|
Thank you to everyone that reviewed this. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
https://bugs.python.org/issue46534
CC @pradeep90 & @JelleZijlstra