diff options
author | wiz <wiz@pkgsrc.org> | 2009-01-07 21:15:49 +0000 |
---|---|---|
committer | wiz <wiz@pkgsrc.org> | 2009-01-07 21:15:49 +0000 |
commit | 70b0ed7464618b284033417dde9f57f7a9fdbd19 (patch) | |
tree | 260db03e341eda7fa70d1f89fa71abb59b1d9532 /doc | |
parent | 86e6ce6164932629985d946d1759027144e3611a (diff) | |
download | pkgsrc-70b0ed7464618b284033417dde9f57f7a9fdbd19.tar.gz |
Update to 4.7.3:
4.7.3: (Python 2.6 release. First release with Python 3.0 support)
* "private" is a keyword in C++. (Duncan Grisby)
* setup.py should install "bsddb.h". (Duncan Grisby)
* "DB_remove" memory corruption & crash. (Duncan Grisby)
* Under Python 3.0, you can't use string keys/values, but
bytes ones. Print the right error message.
* "DB.has_key()" allowed transactions as a positional parameter.
We allow, now, transactions as a keyword parameter also, as
documented.
* Correct "DB.associate()" parameter order in the documentation.
* "DB.append()" recognizes "txn" both as a positional and a
keyword parameter.
* Small fix in "dbshelve" for compatibility with Python 3.0.
* A lot of changes in "dbtables" for compatibility with Python 3.0.
* Huge work making the testsuite compatible with Python 3.0.
* In some cases the C module returned Unicode strings under
Python 3.0. It should return "bytes", ALWAYS. Solved.
* Remove a dict.has_key() use to silence a warning raised under
Python2.6 -3 parameter. Python SVN r65391, Brett Cannon.
* Solve some memory leaks - Neal Norwitz
* If DBEnv creation fails, library can crash. (Victor Stinner)
* Raising exceptions while doing a garbage collection
will kill the interpreter. (Victor Stinner)
* Crash in "DB.verify()". Noted by solsTiCe d'Hiver.
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions