| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
I would suggest that we keep the old syntax but keep the ruff update. Btw ISTM that this new syntax is similar to the old print syntax which was then replaced by the () form so I still struggle to parse this.
Sorry, something went wrong.
There was a problem hiding this comment.
I like the new syntax: it means less noisy punctuation, and it's similar to the way that tuples don't need parentheses to be tuples.
Sorry, something went wrong.
Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
Yeah this kind of syntax is also annoying for me except for destructuring... (I always put parentheses around my tuples except when doing a x, y = ...) At least we agree on not agreeing! I won't block on that change (though I think it's preferrable if we decide which syntax to use because while less noisy it is still hard without it for me to read it (the comma looks like I'm done with my line so my eyes don't parse afterwards. With parentheses, I know I need to find the other closing parenthesis). |
Sorry, something went wrong.
|
I think the SC accepting PEP 758 is a pretty good signal that it's okay to use :) This is modern Python.
Ironically, your full last comment has three opening parentheses, but only two closing ones! Or perhaps an argument for using fewer parentheses ;) |
Sorry, something went wrong.
Yeah I saw that! well it is an argument for using fewer but it won't help me when reading (when writing it could!) |
Sorry, something went wrong.
|
Btw, the only place where I found the missing parentheses in tuples was in the stdlib. I didn't see other codes doing it actually so I never knew about it! (I only learned about it when looking at our tests...) |
Sorry, something went wrong.
Huh, I think it's fairly common to do for a, b in my_dict.items(): ... |
Sorry, something went wrong.
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
|
Thanks @hugovk for the PR, and @AA-Turner for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
|
Sorry, @hugovk and @AA-Turner, I could not cleanly backport this to 3.14 due to a conflict. cherry_picker 81484c5629f9d8b698a2be58f850a0e4efe48ed3 3.14 |
Sorry, something went wrong.
…pythonGH-144656) (cherry picked from commit 81484c5) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
|
GH-144710 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
…n#144656) Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
…n#144656) Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
…n#144656) Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.