[issue19385] dbm.dumb should be consistent when the database is closed
Claudiu.Popa
report at bugs.python.org
Thu Apr 24 07:11:39 CEST 2014
Claudiu.Popa added the comment:
On my machine I get the following results for the unclosed-database case.
With patch:
# ./python -S -m timeit -n 100000 -s "import dbm.dumb as dbm; d=dbm.open('x.dat', 'c');len(d)"
100000 loops, best of 3: 0.0638 usec per loop
Without patch:
# ./python -S -m timeit -n 100000 -s "import dbm.dumb as dbm; d=dbm.open('x.dat', 'c');len(d)"
100000 loops, best of 3: 0.0634 usec per loop
----------
Added file: http://bugs.python.org/file35016/issue19385_1.patch
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19385>
_______________________________________
More information about the Python-bugs-list
mailing list