> Current bsddb module in 2.5.1 supports up to BerkeleyDB 4.5. There is > support for 4.6 in trunk (future 2.6, I guess) and I'm working in a > private branch at the moment, since I have no commit access to python > repository. That private version is intented to be merged into python > 2.6 by Greg, when time comes. > > My guess is that 2.5 branch is still open to more patches than pure > security/stability patches, so "backporting" BerkeleyDB 4.6 support > seems reasonable (to me). If I'm wrong, please educate me :-).
I think it depends on the nature of the patch. The 2.5 branch already supports BerkeleyDB 4.6 (since r58345), so I'm not sure what else needs to be done. > This backport would include also stability patches. For example, I just > solved a memory leak. > > Greg, any opinion?. > > Beware, new kid in the block! :). Being new is not a problem in itself. But do please take the extra work of double- and triple-checking any claims you make. If you want to become the new maintainer of the bsddb module, you need to learn how to check out a branch of Python and how to determine what patches have been applied to it. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
