summaryrefslogtreecommitdiffstats
path: root/Lib/bsddb
Commit message (Collapse)AuthorAgeFilesLines
* Fix idioms and a couple of py3k warnings. Patch by Florent Xicluna.Ezio Melotti2010-02-029-49/+44
|
* #7092: silence py3k warnings for bsddb. Patch by Florent Xicluna.Ezio Melotti2010-02-027-80/+37
|
* #7269: fix failures in test_bsddb3. Patch by Florent Xicluna.Ezio Melotti2010-01-241-1/+1
|
* Issue #7092: Fix the DeprecationWarnings emitted by the standard libraryAntoine Pitrou2010-01-041-1/+1
| | | | when using the -3 flag. Patch by Florent Xicluna.
* Turn the bsddb replication startup timeout test into aR. David Murray2009-11-141-2/+7
| | | | warning, to improve buildbot stability.
* I got the relative magnitudes of the timeout increases reversed, soR. David Murray2009-11-111-1/+1
| | | | | | I'm bumping up the longer test to the 60 seconds I intended to make it. If this doesn't cure the intermittent buildbot timeouts, I'm going to turn that test into a warning rather than a failure.
* Increase the timeout in the bsddb3 replication test to allowR. David Murray2009-11-051-2/+2
| | | | the test time to complete on slow buildbots. See issue 6462.
* Fix py3k warnings in bsddbAntoine Pitrou2009-10-144-119/+112
|
* Issue #5341: Fix a variety of spelling errors.Mark Dickinson2009-02-213-3/+3
|
* Issue #5073: Fix occasional failure of bsddb/test/test_lock.py. ThanksMark Dickinson2009-01-261-1/+1
| | | | Hirokazu Yamamoto for the patch.
* Bugfix for issue3885 and 'DB.verify()' crash.Jesus Cea2008-09-231-16/+36
| | | | Reviewed by Nick Coghlan.
* On Windows, temporarily disable the bsddb test referenced in bug 3892.Mark Hammond2008-09-181-1/+13
| | | | | We do yell to stderr and the bug is marked as a blocker. Reviewed by barry in #python-dev.
* warnings.catch_warnings() now returns a list or None instead of the customBrett Cannon2008-09-091-3/+3
| | | | | | | | WarningsRecorder object. This makes the API simpler to use as no special object must be learned. Closes issue 3781. Review by Benjamin Peterson.
* Deprecate bsddb for removal in Python 3.0.Brett Cannon2008-09-051-0/+6
| | | | | Closes issue 3776. Review by Nick Coghlan.
* Python3.0 bsddb testsuite compatibility improvementsJesus Cea2008-09-031-0/+4
|
* Improve compatibility with Python3.0 testsuiteJesus Cea2008-09-022-6/+11
|
* In Python3.0, "test.test_support" is renamed to "test.support".Jesus Cea2008-09-011-1/+4
|
* Update bsddb code to version 4.7.3pre2. This code shouldJesus Cea2008-08-3124-405/+899
| | | | | | be compatible with Python 3.0, also. http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.7.3
* Remove a dict.has_key() use to silence a warning raised under -3.Brett Cannon2008-08-021-1/+1
|
* Be less strict with replication timeouts (the machineJesus Cea2008-07-291-7/+19
| | | | | can be a bit loaded), and be sure to yield the CPU when waiting.
* Refinements in the bsddb testsuiteJesus Cea2008-07-292-4/+4
|
* bsddb module updated to version 4.7.2devel9.Jesus Cea2008-07-2314-139/+492
| | | | | | | | | | | | | This patch publishes the work done until now for Python 3.0 compatibility. Still a lot to be done. When possible, we use 3.0 features in Python 2.6, easing development and testing, and exposing internal changes to a wider audience, for better test coverage. Some mode details: http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.7.2
* Merged revisions 64368-64369 via svnmerge fromTrent Nelson2008-06-271-1/+1
| | | | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/branches/tnelson-trunk-bsddb-47-upgrade ........ r64368 | trent.nelson | 2008-06-17 23:13:44 -0500 (Tue, 17 Jun 2008) | 1 line Initial commit of work pertaining to switching the Windows build from Berkeley DB 4.4.20 to 4.7.25. Note that I've deprecated the standalone '_bsddb44.vcproj' in lieu of adding the sources in a separate folder to the _bsddb project. This was a conscious decision and actually makes everything far more easier to manage. With this approach, entire test suite passed straight off the bat. Well, almost -- the timeout in bsddb/test/test_replication.py needed bumping up a little -- 2 seconds was too short. 10 seconds seems to be fine for me, but I'll make sure Jesus verifies. More documentation to come once I've been able to test out this approach on the buildbots (hence keeping the changes in a separate branch for now). ........ r64369 | trent.nelson | 2008-06-17 23:19:12 -0500 (Tue, 17 Jun 2008) | 1 line Bump Berkeley DB version from 4.4.20 to 4.7.25. ........
* Better integration between Python testing and bsddb3Jesus Cea2008-05-271-9/+12
|
* Fix issue2669: bsddb simple/legacy interface iteration silently failsGregory P. Smith2008-05-251-63/+77
| | | | | | | when database changes size during iteration. It now behaves like a dictionary, the next attempt to get a value from the iterator after the database has changed size will raise a RuntimeError.
* * Give the test_bsddb3 tests a unique temporary directory to run theirGregory P. Smith2008-05-251-7/+15
| | | | | | | | stuff in and clean it up afterwards regardless of the result. * Get rid of duplicate list of test modules to run, they're maintained within test_all now. * Print the BerkeleyDB version to stderr when running test_bsddb3 to help buildbot problem diagnosis.
* Use test_support to get network ports to bind to.Gregory P. Smith2008-05-251-8/+10
|
* bsddb module updated to version 4.7.0Jesus Cea2008-05-223-4/+4
|
* bsddb: Beware with sequence wrappingJesus Cea2008-05-191-9/+5
|
* issue2858: Fix potential memory corruption when bsddb.db.DBEnv.lock_getGregory P. Smith2008-05-171-7/+1
| | | | | and other bsddb.db object constructors raised an exception. Debugging & patch by Neal Norowitz.
* disable the crashing test. I will also file a bug. This crash doesGregory P. Smith2008-05-151-1/+7
| | | | | | not appear to be a new bug, its just that the test coverage went up recently exposing it. (I verified that by testing this test code on an older Modules/_bsddb.c)
* Testsuite for bsddb module, version 4.6.4Jesus Cea2008-05-1325-714/+1213
|
* #2503 make singletons compared with "is" not == or !=Benjamin Peterson2008-03-293-6/+6
| | | | Thanks to Wummel for the patch
* Make sure that the warnings filter is not reset or changed beyond the currentBrett Cannon2008-03-191-4/+5
| | | | | | running test file. Closes issue2407. Thanks Jerry Seutter.
* Remove the files/dirs after closing the DB so the tests work on Windows.Neal Norwitz2008-03-052-6/+3
| | | | Patch from Trent Nelson. Also simplified removing a file by using test_support.
* Close the file before trying to remove the directory so it works on Windows.Neal Norwitz2008-03-041-1/+2
| | | | As reported by Trent Nelson on python-dev.
* Modify import of test_support so that the code can also be used with aGregory P. Smith2008-03-0215-15/+73
| | | | | stand alone distribution of bsddb that includes its own small copy of test_support for the needed functionality on older pythons.
* Create a db_home directory with a unique name so multiple users canNeal Norwitz2008-02-2415-77/+51
| | | | | | | | | | | | run the test simultaneously. The simplest thing I found that worked on both Windows and Unix was to use the PID. It's unique so should be sufficient. This should prevent many of the spurious failures of the automated tests since they run as different users. Also cleanup the directory consistenly in the tearDown methods. It would be nice if someone ensured that the directories are always created with a consistent name.
* Patch #2167 from calvin: Remove unused importsChristian Heimes2008-02-2316-24/+9
|
* Consistently use tempfile.tempdir for the db_home directory.Neal Norwitz2008-01-265-5/+8
|
* Fix exception in tearDown on ppc buildbot. If there's no directory,Neal Norwitz2008-01-261-2/+5
| | | | that shouldn't cause the test to fail. Just like it setUp.
* * db->get_flags is only available in BerkeleyDB >= 4.2Gregory P. Smith2007-11-051-0/+4
|
* Add the bsddb.db.DBEnv.lock_id_free method.Gregory P. Smith2007-11-051-14/+12
| | | | Improve test_lock's tempdir creation and cleanup.
* Fixes bug 477182 on pybsddb.sf.net. DB objects now load the flags andGregory P. Smith2007-11-051-0/+24
| | | | | | | | | | pay attention to them when opening an existing database. This means that d[] behaves properly even on databases previously created with DB_DUP or DB_DUPSORT flags to allow duplicate keys. http://sourceforge.net/tracker/index.php?func=detail&aid=477182&group_id=13900&atid=113900 Do not backport, this bugfix could be considered an API change.
* Undo revision 58533 58534 fixes. Those were a workaround forGregory P. Smith2007-11-011-3/+2
| | | | a problem introduced by 58385.
* Fix bug introduced in revision 58385. Database keys could no longerGregory P. Smith2007-11-011-4/+21
| | | | | have NULL bytes in them. Replace the errant strdup with a malloc+memcpy. Adds a unit test for the correct behavior.
* squelch the warning that this test is supposed to trigger.Gregory P. Smith2007-10-191-2/+7
|
* A cleaner fix than the one committed last night. Generate random rowids thatGregory P. Smith2007-10-181-5/+6
| | | | do not contain null bytes.
* Fix a weird bug in dbtables: if it chose a random rowid string that containedGregory P. Smith2007-10-181-4/+4
| | | | | NULL bytes it would cause the database all sorts of problems in the future leading to very strange random failures and corrupt dbtables.bsdTableDb dbs.
* cleanup test_dbtables to use mkdtemp. cleanup dbtables to pass txn as aGregory P. Smith2007-10-182-19/+18
| | | | | keyword argument whenever possible to avoid bugs and confusion. (dbtables.py line 447 self.db.get using txn as a non-keyword was an actual bug due to this)
generated by cgit v0.12 at 2024-11-27 13:56:12 (GMT)