From: "Brett Cannon" <[EMAIL PROTECTED]>
I appreciate you want to maintain the code, Jesus, but that still
makes you the single point of failure for the code. If you decide you
don't want to deal with it, or are on vacation when the code breaks
just before a release, it is quite possible we are s
On Sat, Jul 19, 2008 at 1:00 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
[SNIP]
> I acknowledge that some people would like to remove bsddb from the
> standard lib, arguing it is a maintenance nightmare. I consider, then,
> that the right thing to do would be to (fully) delegate this code to me,
> a g
On Sat, Jul 19, 2008 at 1:00 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
>
> Anybody is able to compile current bsddb in 3.0 svn?. May I overwrite
> current version with my own one, updated with your patches (except the
> buffer code; I rather prefer to delay that)?.
>
Yes, feel free to replace it w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 19, 2008, at 4:00 AM, Jesus Cea wrote:
I acknowledge that some people would like to remove bsddb from the
standard lib, arguing it is a maintenance nightmare. I consider, then,
that the right thing to do would be to (fully) delegate this code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm actively working porting current bsddb code to python 3.0. The work
is going fine. Current code compiles in both Python 2.[3-6] and 3.0. I
have some issues with module initialization:
"""
[EMAIL PROTECTED] bsddb3]$ python3.0
Python 3.0b2 (r30b2:6
