]> granicus.if.org Git - python/commit
patch #766650 - whichdb not identifying dbm DBs when dbm linked with gdbm
authorAndrew MacIntyre <andymac@bullseye.apana.org.au>
Fri, 11 Jul 2003 12:16:48 +0000 (12:16 +0000)
committerAndrew MacIntyre <andymac@bullseye.apana.org.au>
Fri, 11 Jul 2003 12:16:48 +0000 (12:16 +0000)
commita1e93e8dfc6daf78a8a46c41aca6e85cede74c02
treec1c78af2a6e8f356aa3ed9510a7d13a02cd8b297
parentc4bf893952743a89f078915583b29594690dfa12
patch #766650 - whichdb not identifying dbm DBs when dbm linked with gdbm

At this point, the problem appears particular to the OS/2 EMX port of
gdbm (which is at v1.7.3) - this combination produces a .pag file but
no .dir file.

A more sophisticated patch which checks magic numbers when dbm.library
indicates that dbm is linked to gdbm, and there is no .dir file, is
still attached to the above patch entry for reconsideration after 2.3
is released.

This checkin applies a workaround specific to the known failure case.
Lib/whichdb.py