I'm -100 now on "deferred evaluation, but contorted to be useless outside of argument declarations." At first I thought it might be harmless, but nothing I really care about. After the discussion, I think the PEP would be actively harmful to future Python features. On Sat, Oct 30, 2021, 3:57 PM Eric V. Smith <eric@trueblade.com> wrote:
On 10/26/2021 7:38 PM, Rob Cliffe via Python-ideas wrote:
PS Can I echo Guido's plea that people don't derail this PEP by trying to shoehorn deferred-evaluation-objects (or whatever you want to call them) into it? As Chris A says, that's a separate idea and should go into a separate PEP. If I need a screwdriver, I buy a screwdriver, not an expensive Swiss Army knife.
As I've said before, I disagree with this. If you're going to introduce this feature, you need some way of building an inspect.Signature object that refers to the code to be executed. My concern is that if we add something that has deferred evaluation of code, but we don't think of how it might interact with other future uses of deferred evaluation, we might not be able to merge the two ideas.
Maybe there's something that could be factored out of PEP 649 (Deferred Evaluation Of Annotations Using Descriptors) that could be used with PEP 671?
That said, I'm still -1 on PEP 671.
Eric
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-leave@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/CCFPVN... Code of Conduct: http://python.org/psf/codeofconduct/