>From the article: > "a Python Enhancement Proposal (PEP) was created to postpone their > evaluation until they were needed. The PEP-described behavior was set to > become the default in the upcoming Python 3.10 release, but that is not to > be; the postponement of evaluation by default has itself been postponed in > the hopes of unwinding things."
The present objection to PEP 649 is its breaking change to the *__annotations__* attribute, since that attribute has been around since Python 3.0 and its use not restricted to types. Perhaps adding two attributes to objects would work: one would be the *__co_annotations__* attribute described in PEP 649, the other would be a typing-specific attribute with use limited to typing, that would for that use take the place of the existing *__annotations__* attribute. This would require work by the authors of code that relies on the current *__annotations__* attribute for typing-related information, but that may be the only sure answer that does not break code that uses the *__annotations__* attribute for other purposes. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/9ff058d8-644a-4070-8eb1-f4f4025904efn%40googlegroups.com.
