New submission from Jesús Cea Avión <j...@jcea.es>: This issue tracks the progress of integration of pybsddb 4.8.3+ and centralize related discussion.
I have integrated all bsddb related patches until r78988, in pybsddb 4.8.3+, with the following caveats: - The new code supports BDB 4.8, but drops support for 4.0. Berkeley DB 4.0 was released in 2001... - Revert issue6949 (the 2.7 part). This integration work supercedes it. - issue6462 is not integrated in pybsddb, but will be retained in the code integrated in python. I will try to resolve it in a permanent way after integration. - issue3892 is not integrated in pybsddb, but will be retained in the code integrated in python. I will try to resolve it in a permanent way after integration. - issue7975: I can't reproduce this bug with current pybsddb version. I will keep the patch around, but first integration test will not include it, unless we still can reproduce. Some changes in bsddb testsuite require 2.7/3.2. I have decided to keep the changes, so I have to backport some code and use conditional execution, because I must support python 2.3-2.7 and 3.0-3.2. ---------- assignee: jcea components: Extension Modules messages: 101166 nosy: jcea severity: normal stage: patch review status: open title: pybsddb 4.8.3+ integration type: feature request versions: Python 2.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8156> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
