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 petr.viktorin
Recipients Alexander.Belopolsky, Arfrever, Christian.Tismer, Robin.Schreiber, amaury.forgeotdarc, belopolsky, haberman2, jcea, jhaberman, lekma, loewis, mattip, petr.viktorin, pitrou, seberg, steve.dower
Date 2021-10-12.13:28:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The new issue is bpo-45383.

There's a sprint newt week; I'll probably get to it then.

> But, I am trying to understand the preference for static better.  There is probably something to learn or even important I am missing.

The original motivating use case is not "create types dynamically on demand", but "create types without details of the C structure being compiled into the extension". That is, make it possible for modules to be compatible with several versions of Python.
The spec is designed to be extensible; the type struct is designed to be fast at runtime.

> And I have some plans to make static specs useful in type checking

This is quickly getting out of scope here, but if you're interested, I put down some notes here:
Date User Action Args
2021-10-12 13:28:38petr.viktorinsetrecipients: + petr.viktorin, loewis, jcea, amaury.forgeotdarc, belopolsky, pitrou, Arfrever, lekma, Alexander.Belopolsky, mattip, Robin.Schreiber, steve.dower, seberg, Christian.Tismer, jhaberman, haberman2
2021-10-12 13:28:38petr.viktorinsetmessageid: <>
2021-10-12 13:28:38petr.viktorinlinkissue15870 messages
2021-10-12 13:28:38petr.viktorincreate