summaryrefslogtreecommitdiffstats
path: root/Lib/whichdb.py
Commit message (Collapse)AuthorAgeFilesLines
* catch the situation where Berkeley DB is used to emulate dbm(3) librarySkip Montanaro2002-08-021-3/+24
| | | | | functions. In this case, calling dbm.open("foo", "c") actually creates a file named "foo.db".
* SF patch #474590 -- RISC OS supportGuido van Rossum2001-10-241-9/+4
|
* Whitespace normalization.Tim Peters2001-03-161-1/+1
|
* RISCOS changes by dschwertberger.Guido van Rossum2001-03-021-4/+11
|
* move import into function to avoid having to add an __all__ list...Skip Montanaro2001-03-011-2/+2
|
* Add missing 'try:'. Patch by Rob W. W. Hooft, #101071 (closed.)Thomas Wouters2000-08-041-0/+1
|
* Added support to recognize Python's internal "dumbdbm" database.Moshe Zadka2000-07-291-0/+12
| | | | This closes bug 200 on Jitterbug.
* Untabify to pass the -tt test.Fred Drake2000-02-101-1/+1
|
* Skip Montanaro:Guido van Rossum1999-06-081-2/+13
| | | | | | | | | I guess in 1.5.2 a new module, whichdb, was added that attempts to divine the nature of a database file. This module doesn't know anything about Berkeley DB v2 files. In v2, Sleepycat added a 12-byte null pad in front of the old magic numbers (at least for hash and btree files). I've been using v2 for awhile and upgrading to 1.5.2 broke all my anydbm.open calls. I believe the following patch corrects the problem.
* Support byte-swapped dbhash (bsddb) files. Found by Ben Sayer.Guido van Rossum1998-04-281-1/+1
|
* Mass check-in after untabifying all files that need it.Guido van Rossum1998-03-261-13/+13
|
* Use new struct which supports standardized sizesGuido van Rossum1997-01-111-5/+2
|
* Function to guess which db package created a database.Guido van Rossum1996-07-301-0/+60