Jesús Cea Avión added the comment:
I found the very same bug recently, and solve it in pybsddb 4.8.3. My patch is
exactly like this :).
The problem will be solved in 2.7 when I integrate pybsddb 4.8.3/4.8.4. Not
sure about 2.6, though. Will try.
"""
changeset: 478:a35a9082ee26
user:
New submission from Paul Colomiets :
When maximum transaction number exceeded and DBEnv->txn_begin returns
with error ENOMEM, error with following traceback occur:
#0 0x000803d4fa48 in DBTxn_dealloc (self=0x846480648) at _bsddb.c:1235
#1 0x000803d506dc in newDBTxnObject (myenv=0x804c23
