Benjamin Peterson <[email protected]> added the comment: 2010/9/23 Antoine Pitrou <[email protected]>: > > Antoine Pitrou <[email protected]> added the comment: > > Actually, it is because bz2 doesn't call PyType_Ready() but instead sets some > field manually. Perhaps we could have a guard somewhere that raises a fatal > error when a C extension type hasn't been properly readied?
The problem is that there's no one entry point for types to get into the C-API. I suppose we could iterate through a c-module's dictionary after it's initialized... > > In the meantime, this patch seems to solve the issue: Please apply. ---------- _______________________________________ Python tracker <[email protected]> <http://bugs.python.org/issue9928> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
