This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients eric.smith, gvanrossum, larry
Date 2021-04-21.20:26:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1619036783.49.0.155942445659.issue43901@roundup.psfhosted.org>
In-reply-to
Content
Sounds like a plan, I agree that the original design misfired here (we were probably worried about million-line code bases with tens of thousands of classes having to pay the price of tens of thousands of empty dicts, but I now think that was an unnecessary worry -- that should be a few megabytes on a very much larger total).

But given that you're not done yet:

- Is it possible to create __annotations__ lazily? (IIRC in January we came to a conclusion about this, something like yes for modules but for classes, or the other way around?)

- Why would __annotations__ ever be None? Why do you allow setting it to None? Do we know of people ever write '__annotations__ = None' in their class or write 'cls.__annotations__ = None'?

- And where's your PR?
History
Date User Action Args
2021-04-21 20:26:23gvanrossumsetrecipients: + gvanrossum, larry, eric.smith
2021-04-21 20:26:23gvanrossumsetmessageid: <1619036783.49.0.155942445659.issue43901@roundup.psfhosted.org>
2021-04-21 20:26:23gvanrossumlinkissue43901 messages
2021-04-21 20:26:22gvanrossumcreate