Petr Viktorin <encu...@gmail.com> added the comment:
> 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.) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue45315> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
