Message 184702 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	jcea
Recipients	barry, benjamin.peterson, dmalcolm, doko, gregory.p.smith, jcea, python-dev
Date	2013-03-19.23:10:10
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1363734610.44.0.174381682241.issue17477@psf.upfronthosting.co.za>
In-reply-to

Content
Berkeley DB 6.0 is inminent. A month or two. Is this a backport "as-is" of the external pybsddb3 5.3.0 code I maintain?. If that is the case, could be some incompatibilities with current bsddb module in stock 2.7. I don't care (a lot) anymore keeping compatibility, now that pybsddb3 is an external project. My code doesn't have some patches done in cpython version. Beware, you could revert them by mistake.

Berkeley DB 6.0 is inminent. A month or two.

Is this a backport "as-is" of the external pybsddb3 5.3.0 code I maintain?. If that is the case, could be some incompatibilities with current bsddb module in stock 2.7. I don't care (a lot) anymore keeping compatibility, now that pybsddb3 is an external project.

My code doesn't have some patches done in cpython version. Beware, you could revert them by mistake.

History
Date	User	Action	Args
2013-03-19 23:10:10	jcea	set	recipients: + jcea, barry, doko, gregory.p.smith, benjamin.peterson, dmalcolm, python-dev
2013-03-19 23:10:10	jcea	set	messageid: <1363734610.44.0.174381682241.issue17477@psf.upfronthosting.co.za>
2013-03-19 23:10:10	jcea	link	issue17477 messages
2013-03-19 23:10:10	jcea	create