Hello, On Thu, 12 Nov 2020 12:51:19 -0800 Guido van Rossum <gu...@python.org> wrote:
> I have a meta-observation. Clearly there are too many cooks here. The > same suggestions keep getting brought up. We will never converge on a > design this way. Right, it's not a Python decision unless it's forced thru like PEP572, aka the ":=" (https://lwn.net/Articles/757713/ , etc.). Can also remember the whole Python3 migration business (https://gregoryszorc.com/blog/2020/01/13/mercurial%27s-journey-to-and-reflections-on-python-3/ , etc). > At this point the only thing to do is to wait for > the Steering Council. I am not going to argue about the merits of any > more specific ideas -- everything has already been proposed and the > PEP authors have come up with a design that carefully weighs a *lot* > of different requirements. Right, PEP622, PEP634, PEP635, PEP636 are very well written and discuss many options thoroughly. The sentiment that many people on the list have is that they then make a particular choice (like a PEP has to do of course), while there're other very viable choices (and one proposed by PEP has glaring adhockery). So, maybe, just maybe, it's too early yet to shut on one option, and would be beneficial to keep considering other options open-mindedly (for the PEP authors first of all, as clearly, there won't a competing PEP proposal). So, while we keep waiting for SC, we can remember the short history of the mentioned PEP572. At times of PEP622, ":=" was touted as something like enabler for the whole pattern matching business, as that's what allows to do things like: "case [1, y := (1, x), 2]". The suddenly, PEP634 silently (well, without much ado) replaces it with the "as" keyword. So much for the great enabler. And now ":=" keeps sticking a square peg in a round hole of the language, with this: (a, b) = (1, 2) - possible, and this: ((a, b) := (1, 2)) - oopsing: File "<stdin>", line 1 SyntaxError: cannot use assignment expressions with tuple Current PEP634 offers the same level of the language consistency and generality, with random (but practical, if you believe the PEP authors) hacks sprinkled around instead. -- Best regards, Paul mailto:pmis...@gmail.com _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/YN7QQXNSWDFZNP75MRZC7AQPGBRU2H7S/ Code of Conduct: http://python.org/psf/codeofconduct/
