[issue19385] dbm.dumb should be consistent when the database is closed

[Jim Jewett]

Jim Jewett added the comment:

Did you try 3.5 without the patch, in case the issue is not with his code?
On May 13, 2014 7:23 AM, "Serhiy Storchaka" <report at bugs.python.org> wrote:

>
> Serhiy Storchaka added the comment:
>
> Claudiu, your benchmark is broken, it measure a no-op.
>
> Correct benchmark:
>
>     $ ./python -S -m timeit -n 100000 -s "import dbm.dumb as dbm;
> d=dbm.open('x.dat', 'c')"  "len(d)"
>
> 3.4:  100000 loops, best of 3: 2.56 usec per loop
> 3.5:  100000 loops, best of 3: 4.17 usec per loop
>
> There is 60% regression.
>
> ----------
> status: closed -> open
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue19385>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19385>
_______________________________________