Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-April/035094.html below:

[Python-Dev] New thread death in test_bsddb3

• Previous message: [Python-Dev] New thread death in test_bsddb3
• Next message: [Python-Dev] Magic number needs upgrade
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> 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.

Mark.

• Previous message: [Python-Dev] New thread death in test_bsddb3
• Next message: [Python-Dev] Magic number needs upgrade
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4