Senthil Kumaran orsent...@gmail.com added the comment:
Fixed in revision 88631
--
nosy: +orsenthil
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Antoine Pitrou pit...@free.fr added the comment:
Can you backport to 3.2?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10228
___
___
Senthil Kumaran orsent...@gmail.com added the comment:
Done in r88634.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10228
___
___
Ray.Allen ysj@gmail.com added the comment:
It looks like because before the second time running of
WhichDBTestCase.test_whichdb(), previous dumb files are not cleaned clearly, so
the gdbm's open() doesn't create a new gdbm database but open an existing dumb
database.
In fact during the
Changes by Michael Foord mich...@voidspace.org.uk:
--
nosy: -michael.foord
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10228
___
___
Éric Araujo mer...@netwok.org added the comment:
A quick look makes me think the bug is in the test, not the code.
--
nosy: +eric.araujo, giampaolo.rodola, michael.foord
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10228
New submission from Antoine Pitrou pit...@free.fr:
This is only when several dbm modules are compiled in (e.g. gnu and dumb):
$ ./python -m test.regrtest -R 3:2 test_dbm
[1/1] test_dbm
beginning 5 repetitions
12345
test test_dbm failed -- Traceback (most recent call last):
File
