[pybsddb] Request For Comments: Deprecation of BerkeleyDB pre-4.0

[Jesus Cea]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all.

pybsddb is supposed to support 3.* and 4.* Berkeley DB versions, but the
support is currently broken for 3.* ones. The code doesn't compile, ever.

Since Berkeley DB 4.0 was published six years ago (late 2001), I was
wondering that my time would be best spent improving 4.* support rather
than trying to keep 3.x onboard.

As I already said, 3.x doesn't compile, actually, and I have no reports
of problems about that. What do you think?.

My points:

* Current 3.x support is broken. The code doesn't compile.

* 4.0 was released in late 2001. Six years ago.

* Anybody using Berkeley DB 3.* is using an ancient installation. Her
current tools/applications are outdated but if he finds them
appropriate, doesn't need to upgrade. So dropping support is a non issue
for such an user.

* A Berkeley DB 3.x environment can be easily upgraded to 4.x via a
single command ("db_upgrade").

* Dropping 3.x support (currently broken) will simplify pybsddb code.

* My test machinery only test Berkeley DB 4.*.

Opinions?.

I was wondering also about changing the lib name from "bsddb3" to
"bsddb4", to reflect the fact. This would require to update
applications. Opinions?.

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
~                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR+tss5lgi5GaxT1NAQJ8DwP/TxpnovTWXY6CclhOyaJXwGcIJOp9ubN0
5UKOY4ftDOTlri51Y+o/i4kL+v95EQvvkT5rFg1wYhEG3oRgtAT6aBc8OCfogXTk
K1rv9G/lE5qtbaxztm4HUhbbI+KrMv69uDFf2iaAonbgAtVFKoNSCZR9cljihutJ
4OvVuZ0Sjrg=
=x2K+
-----END PGP SIGNATURE-----