Serhiy Storchaka added the comment: This restriction was added because bad thing could happen when statically allocated class inherits dynamically allocated class. I don't remember the number of the issue where such example was exposed, may be Alex remember it.
Likely pygobject creates classes in not safe manner. It would be more correct to create pygobject classes with PyType_FromSpec(), but current code worked for it for years. May be it is not so easy to change pygobject. So may be we should revert changes in 2.7 or convert the error to the deprecation warning. Is there similar issue with 3.4? There may be difference due to the difference of the lifetime of types in 2.x and 3.x. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22079> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
