> just had reason to be looking at dumbdbm.py - perhaps > "terminallybrokendbm.py" would be a better name. There's a whole host of > "oh. my. god." type things in there that are just broken, with massive > dataloss problems if you end up (innocently) getting it from anydbm.py. > > I'm going to fix it either this arvo/evening or tomorrow, but it really > shouldn't go out as part of 2.2 in it's current form. Is it too late to > consider either fixing it or removing it from anydbm's list? Please fix it. It was never intended to be production quality. But it has found more use than it should. Then again, dbhash.py isn't much better...[*] :-( --Guido van Rossum (home page: http://www.python.org/~guido/) [*] http://www.sleepycat.com/historic.html
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