After upgrading to 10.5, a peculiar problem with the "anydbm" module in python has emerged.
A sample run using an existing database :
The database is opened and contains at fist no keys, ie. returns an empty dictionary.
When checking for a specific key, it is is found. After that only one other key is visible. The visible key is NOT the same as found using the key directly.
The code using the anydbm worked flawlessly under 10.4 and python 2.4.
Any suggestions ?
B.
A sample run using an existing database :
Code:
>>> db = anydbm.open("SENSOR_DB","r")
>>> db.keys()
[]
>>> db.has_key("Epsilon.local__20071115:15:09:32")
1
>>> db.keys()
['Epsilon.local__20071115:15:03:07']The database is opened and contains at fist no keys, ie. returns an empty dictionary.
When checking for a specific key, it is is found. After that only one other key is visible. The visible key is NOT the same as found using the key directly.
The code using the anydbm worked flawlessly under 10.4 and python 2.4.
Any suggestions ?
B.
