| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
be compatible with Python 3.0, also.
http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.7.3
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
the Lib/bsddb/test directory
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The problem is that _DB_get_type() can't be called without the GIL
because it calls a bunch of PyErr_* APIs when an error occurs.
There were no other cases in this file that it was called without the GIL.
Removing the BEGIN/END THREAD around _DB_get_type() made everything work.
Will backport.
|
| |
|
|
|
|
|
|
|
|
| |
features in BerkeleyDB not exposed. notably: the DB_MPOOLFILE interface
has not yet been wrapped in an object.
Adds support for building and installing bsddb3 in python2.3 that has
an older version of this module installed as bsddb without conflicts.
The pybsddb.sf.net build/packaged version of the module uses a
dynamicly loadable module called _pybsddb rather than _bsddb.
|
| |
|
|
| |
so merge from the bsddb-bsddb3-schizo-branch back to the trunk.
|
| |
|
|
| |
version 4.1.1 and works with up to BerkeleyDB 4.1.25.
|
| | |
|
| |
|
