I would like to thank everyone who responded to me for their civilised and courteous replies. I actually expected to get a lot of slagging off, but was prepared to accept that for what seemed to me at the time to be a legitimate concern. If my fears were unfounded, I am delighted. If I have been unfair to Guido and the other developers (and it seems that I probably have), I apologise. Thank you. FWIW: I am not against the PEP. I do not have a personal axe to grind, in the form of my own pet idea which I want to see incorporated. I don't like the .name syntax (grit on Tim's monitor; does not suggest the meaning). Nor am I keen on "expressions" being interpreted differently after 'case' than elsewhere in Python. But I don't know what syntax (where necessary) to suggest. I'm not keen on special treatment of the '_' variable, and would prefer to be able to use 'else:' after 'match'. Best wishes Rob Cliffe On 03/07/2020 15:56, Chris Angelico wrote:
The PEP is still a draft and has not been accepted. Don't worry, the normal process is still happening :)
Having a reference implementation is a HUGE help, because people can play around with it. There's a fork running an interactive playground so you can go right now and get a feel for the way the syntax works.
The implementation has *not* been merged into the CPython trunk. It's not a fait accompli - it's a tool to help people evaluate the proposal (and all of the different variants of the proposal as it evolves).
Speaking with my PEP Editor hat on, I would be *thrilled* if more proposals came with ready-to-try code. Only a very few have that luxury, and a lot of the debating happens with nothing but theory - people consider what they *think* they'd do, without actually being able to try it out and see if it really does what they expect. Having a reference implementation isn't necessary, of course, but it's definitely a benefit and not a downside. Also, there HAVE been proposals with full reference implementations that have ended up getting rejected; it's not a guarantee that it'll end up getting merged.
Hope that lessens your fears a bit :)
ChrisA _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/E5U5Z6RR... Code of Conduct: http://python.org/psf/codeofconduct/