Brett,
I goofed a bit in my (private) note to you yesterday. anydbm._name isn't of
interest. It's anydbm._defaultmod. On my system, if I mv Lib/bsddb to
Lib/bsddb- I no longer have the bsddb package available (as you said you
didn't). In that situation, for me, anydbm._defaultmod is the gdbm module.
All three tests succeed:
% ./python.exe ../Lib/test/test_bsddb185.py
test_anydbm_create (__main__.Bsddb185Tests) ... ok
test_open_existing_hash (__main__.Bsddb185Tests) ... ok
test_whichdb (__main__.Bsddb185Tests) ... ok
If I delete gdbm.so I get dbm as anydbm._defaultmod. Again, success:
% ./python.exe ../Lib/test/test_bsddb185.py
test_anydbm_create (__main__.Bsddb185Tests) ... ok
test_open_existing_hash (__main__.Bsddb185Tests) ... ok
test_whichdb (__main__.Bsddb185Tests) ... ok
Delete dbm.so. Run again. Now dumbdbm is anydbm._defaultmod. Run again.
Success again:
% ./python.exe ../Lib/test/test_bsddb185.py
test_anydbm_create (__main__.Bsddb185Tests) ... ok
test_open_existing_hash (__main__.Bsddb185Tests) ... ok
test_whichdb (__main__.Bsddb185Tests) ... ok
In short, I can't reproduce your error. Can you do some more debugging to
see why your anydbm.open seems to be calling bsddb185.open?
Thx,
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4