| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I confirm I am sponsoring this PEP 👍 |
Sorry, something went wrong.
|
Please use PEP number 705. (Re-allocating from #2988 which was closed because it didn't yet find a sponsor.) |
Sorry, something went wrong.
There was a problem hiding this comment.
Standard reminder: You can directly apply all the suggestions you want in one go with Files changed -> Add to batch -> Commit
Sorry, something went wrong.
There was a problem hiding this comment.
This looks quite good and makes a convincing case for the feature, but I have a few comments.
Sorry, something went wrong.
|
Just to note I'm still addressing the feedback, just tackled the easier stuff first! |
Sorry, something went wrong.
There was a problem hiding this comment.
Standard reminder: You can directly apply all the suggestions you want in one go with Files changed -> Add to batch -> Commit
Looking good so far! Just a couple quick suggestion followups to the existing fixes, aside from the bigger pending items. Thanks!
Sorry, something went wrong.
Thanks @alicederyn ! I've resolved the implemented suggestions and checked the corresponding boxes in the checklist above. Just FYI, to help make the easy stuff even easier, in case you aren't aware—instead of recreating the suggestions manually, you can apply them all directly in one go by going to the Files changed tab, clicking Add to batch on the suggestions you want, and then clicking Commit once you've selected all of them. This also auto-resolves the linked review comments, so they don't need to be double-checked and resolved manually. |
Sorry, something went wrong.
Thanks! I was aware of this, but I wanted to check everything rendered correctly locally and iterate, so I did it in the form of a PR to my PR branch. Sorry for creating extra work! |
Sorry, something went wrong.
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
|
For reference, I have a bit of a rewrite at alicederyn#4 to address @JelleZijlstra's comments. I'm getting some internal feedback on it before I merge here, but happy for anyone to comment there first. |
Sorry, something went wrong.
Define what TypedMapping does support, not just what it doesn't, to clarify edge cases like ``|``.
All blocking changes resolved, thanks!
There was a problem hiding this comment.
LGTM from me, aside from still missing a number of recommended sections (see the checklist above) that would likely be quite helpful to include, even if just briefly for each. But that's ultimately up to you, @JelleZijlstra and @pablogsal .
Sorry, something went wrong.
|
Backcompat and reference implementation sections at alicederyn#5 for internal review |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks! Just "Security Implications" (which can be a very brief explanation of why there are none, or mentioning how this might improve user security) and "How to Teach This" suggested sections left, assuming there isn't a reason to omit them. Plus, a couple small suggestions/comments.
Sorry, something went wrong.
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com> Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
|
@CAM-Gerlach I added a "How to teach" section. Pablo suggested leaving out the "security implications" section as it would be empty. |
Sorry, something went wrong.
There was a problem hiding this comment.
A couple last comments/suggestions from my side; otherwise this LGTM!
Sorry, something went wrong.
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
There was a problem hiding this comment.
Thanks for all your hard work on this, @alicederyn ! @JelleZijlstra might have some last comments, but as far as I'm concerned, LGTM!
Sorry, something went wrong.
There was a problem hiding this comment.
I have a few more comments but those could also be addressed later. If you would prefer to have the PEP merged now, let me know and I'll do it.
Sorry, something went wrong.
* Remove `typing_extensions` implementation details; this is more than is necessary for the PEP. * Do not mandate adding the PEP to the `typing` module docs, in case that practice ends before the PEP lands. Left in as a suggestion to mirror PEP 692.
|
"Request rereview" has apparently changed behaviour and I have no idea how it now works :/ Apologies if I spammed anyone. |
Sorry, something went wrong.
Would be curious what specifically you're referring to—I've used this feature routinely over the past several years and haven't noticed any significant UI/UX changes, including just now on this PEP. Though, perhaps it had something to do with the fact that we both triggered it right around the same time, with me having loaded the page prior to you pressing the button? |
Sorry, something went wrong.
|
I hit the request review icon for hugovk and Jelle as usual, but the end state was as if I hadn't, and this is the description of what I apparently did. Maybe it work differently if you have different privileges, and I've just never seen it before because I normally do this on repos where I have edit privileges? |
Sorry, something went wrong.
|
I've definitely seen this behaviour change a week ago in a private GH server, and those usually lag public GH changes by about a half year. |
Sorry, something went wrong.
|
Hmm, strange. I've put in a request about it to the others and GitHub. |
Sorry, something went wrong.
|
Congratulations @alicederyn , your PEP is now live at https://peps.python.org/pep-0705/ ! Now's the time to open a PEP discussion thread on Typing-SIG and/or the PEP category of the Python Discourse, and link it in the Discusions-To and the Post-History here. Thanks! |
Sorry, something went wrong.
|
Thank you @CAM-Gerlach and @JelleZijlstra for your time and feedback! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Proposal to add a TypedMapping protocol to the language.
Sponsor: @pablogsal