| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed by Nick Coghlan.
|
|
|
|
|
| |
We do yell to stderr and the bug is marked as a blocker.
Reviewed by barry in #python-dev.
|
|
|
|
|
|
|
|
| |
WarningsRecorder object. This makes the API simpler to use as no special object
must be learned.
Closes issue 3781.
Review by Benjamin Peterson.
|
|
|
|
|
| |
Closes issue 3776.
Review by Nick Coghlan.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
be compatible with Python 3.0, also.
http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.7.3
|
| |
|
|
|
|
|
| |
can be a bit loaded), and be sure to yield the CPU
when waiting.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
........
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
and other bsddb.db object constructors raised an exception.
Debugging & patch by Neal Norowitz.
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
| |
Thanks to Wummel for the patch
|
|
|
|
|
|
| |
running test file.
Closes issue2407. Thanks Jerry Seutter.
|
|
|
|
| |
Patch from Trent Nelson. Also simplified removing a file by using test_support.
|
|
|
|
| |
As reported by Trent Nelson on python-dev.
|
|
|
|
|
| |
stand alone distribution of bsddb that includes its own small copy of
test_support for the needed functionality on older pythons.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
that shouldn't cause the test to fail. Just like it setUp.
|
| |
|
|
|
|
| |
Improve test_lock's tempdir creation and cleanup.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
a problem introduced by 58385.
|
|
|
|
|
| |
have NULL bytes in them. Replace the errant strdup with a
malloc+memcpy. Adds a unit test for the correct behavior.
|
| |
|
|
|
|
| |
do not contain null bytes.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
was useless due to inverted logic. Also adds a test case for RECNO dbs
to test_dbshelve.
|
|
|
|
| |
sourceforge pybsddb patch 1551443 by w_barnes.
|
|
|
|
|
|
| |
string key (and probably a few other situations with string keys).
This was reported with a patch as pybsddb sourceforge bug 1708868 by
jjjhhhlll at gmail.
|
| |
|
|
|
|
| |
windows happy.
|
| |
|
|
|
|
| |
sandboxes when bsddb3 tests are run.
|