[issue17198] dbm.whichdb references unitialized 'ndbm' variable

Roundup Robot added the comment: New changeset 65fce1dad331 by Ezio Melotti in branch '3.3': #17198: Fix a NameError in the dbm module. Patch by Valentina Mukhamedzhanova. http://hg.python.org/cpython/rev/65fce1dad331 New changeset e91e9b9ba180 by Ezio Melotti in branch 'default': #17198: merge

[issue17198] dbm.whichdb references unitialized 'ndbm' variable

Ezio Melotti added the comment: Fixed, thanks for the patch! -- assignee: -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed versions: -Python 3.2 ___ Python tracker

[issue17198] dbm.whichdb references unitialized 'ndbm' variable

Valentina Mukhamedzhanova added the comment: I added a testcase to demonstrate the bug and an import of ndbm to dbm.__init__.py to fix the bug. -- nosy: +umi Added file: http://bugs.python.org/file30839/patch_17198 ___ Python tracker

[issue17198] dbm.whichdb references unitialized 'ndbm' variable

R. David Murray added the comment: Well, that test works only on 3.2/3.3, because by 3.4 the ndbm variable is only referenced in the second try; make it 'touch foo.db' instead for 3.4. -- ___ Python tracker __

[issue17198] dbm.whichdb references unitialized 'ndbm' variable

R. David Murray added the comment: By the way, this will demonstrate the bug: touch foo.pag python -m dbm.__init__ foo Perhaps that could be the basis for the test (using subprocess). -- stage: -> needs patch title: dbm.whichdbm references non-existent 'ndbm' -> dbm.whichdb refere