-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sep 3, 2008, at 7:01 PM, Jesus Cea wrote:
Barry Warsaw wrote:
and I know Brett agrees, so that's it. On IRC, I've just asked Benjamin to do the honors for 3.0 and Brett will add the deprecations for 2.6.
I just committed the fix for bsddb testsuite in Python 3.0 branch: http://www.python.org/dev/buildbot/3.0.stable/changes/2687
Can I do anything to revert this decision?. If not, what can I do to be reconsidered in 3.1?.
Start raising some pitchforks. It looks like Raymond will join the march :).
Really, this is about what's best for Python and pybsddb. In this article, Guido unambiguously states his opinion:
"+1. In my recollection maintaining bsddb has been nothing but trouble right from the start when we were all sitting together at "Zope Corp North" in a rented office in McLean... We can remove it from 3.0. We can't really remove it from 2.6, but we can certainly start end-of-lifing it in 2.6."
Jesus, let me stress that IMO this is not a reflection on your work at all. On the contrary, keeping it alive in 2.x and providing a really solid independent package for 3.0 is critical for its continued relevance to Python programmers.
I completely agree with Guido that bsddb (not pybsddb) has been a headache since forever. For example, IIRC Sleepycat was notorious for changing the API in micro releases, though I don't know if that's still the case with the current maintainers. I personally believe that Python and pybsddb are both better off with their own maintenance lifecycles so I stand by my decision that pulling it out of 3.0 is the right thing to do. 3.1 is far enough away that any decision we make in 3.0 can be re-evaluated.