On Sun, Oct 31, 2021, 5:39 PM Rob Cliffe via Python-ideas

> PEP 671 will be USEFUL to Python programmers.  We want it!  (When do we
> want it?  Now!)
>

This feels dishonest. I believe I qualify as a Python programmer. I started
using Python 1.4 in 1998. The large majority of my work life since then had
been programming Python. I've written a bunch of books on Python. I was a
director of the PSF.

I DO NOT want PEP 671, and do not feel it would be a net benefit to Python
programmers.

I am not on the SC, so indeed I won't make the decision. But I *will*
continue to teach Python. New syntax adds a burden to learners, and it
should not be introduced without sufficient benefit to merit that burden.
This proposal does not come close to that threshold.

I was the first in this thread to propose a far more general capability
that I think WOULD meet the cost/benefit balance... and I proposed it
because I think there is a way to meet the niche need that also has wide
enough application to warrant new syntax.

Python isn't Perl. Not every piece of syntax that *someone* might
occasionally use for a narrow need should be included in the language.

>
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at 
https://mail.python.org/archives/list/python-ideas@python.org/message/TN4TZBP45BIA33AIEYSD2L77FQVWHVJN/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to