Message403734
> Hm, I haven't find any case who use dynamical tp_name of Type_Spec temporarily.
The use case is creating types entirely on demand, with dynamically created specs.
This is useful e.g. for wrapping objects of a different object system, like C++ classes or Qt/GTK widgets.
But this issue is not about adding new API to enable a new use case. The *current* API can reasonably be used with a dynamic name string. So we shouldn't wait until someone tells us they need this fixed :)
So this should either be fixed or the requirement should be documented. (And the documentation would IMO sound like we're acknowledging a design bug, so it's better to fix.) |
|
Date |
User |
Action |
Args |
2021-10-12 13:49:36 | petr.viktorin | set | recipients:
+ petr.viktorin, seberg, shihai1991 |
2021-10-12 13:49:36 | petr.viktorin | set | messageid: <1634046576.21.0.735810918659.issue45315@roundup.psfhosted.org> |
2021-10-12 13:49:36 | petr.viktorin | link | issue45315 messages |
2021-10-12 13:49:36 | petr.viktorin | create | |
|