[Python-Dev] Berkeley DB

[Guido van Rossum]

> 1) Give up and do nothing
> 2) Try fixing SWIG.
> 3) Include the SWIG-generated code as it stands
> 4) Write a custom new BerkeleyDB extension.  (In time for 2.0b1?  Iffy...)
> 
> I think the only solution is to do the job right and do #4, though it
> might wind up being postponed until Python 2.1, or whatever comes
> after 2.0.

Is the existing 3rd party BerkeleyDB broken, or just stylistically too
bad for inclusion in the core?  If the latter, we could remove bsddb
from the core and refer to the 3rd party module -- assuming it has a
website and all.

--Guido van Rossum (home page: http://dinsdale.python.org/~guido/)