[Python-Dev] New thread death in test_bsddb3
Sat, 26 Apr 2003 10:16:50 +1000
> So is the policy now that it is no longer *allowed* to create another
> thread state, while in previous versions there wasn't any choice,
> because there existed no way to get the existing one?
Only not allowed under debug builds <wink>.
I would be more than happy to have this code print a warning, or take some
alternative action - but I would hate to see the message dropped.
Would a PyErr_Warning call be more appropriate? The only issue here is that
literally *thousands* may be generated.