<br><div><span class="gmail_quote">On 1/10/08, <b class="gmail_sendername">Guido van Rossum</b> <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Jan 10, 2008 4:52 AM, Jesus Cea <<a href="mailto:jcea@argo.es">jcea@argo.es</a>> wrote:<br>> I'm very dependent of bsddb support in python. I'm very sorry also of<br>> the maintainer support of it: he is slow and doesn't implement python
<br>> bindings for berkeleydb features deployed five years ago :-(. Could be a<br>> bit rude, but maybe a maintaner change would be in order. I would rather<br>> prefer to talk to current maintainer, but I rather apply for maintaner
<br>> position than dropping bsddb from the python stdlib!!.<br><br>Hi Jesus,<br><br>I don't know if there *is* a current maintainer. There are a few<br>people who sometimes fix things in the current code base, but I think
<br>development has stopped. If you're serious about wanting to take over<br>maintenance, (or even just contributing) that would be great!</blockquote><div><br>I consider myself the maintainer because I at least make sure it keeps working with new berkeleydb releases and such and am one of the most familiar with the _bsddb.c code internals (both the good and the bad).
<br><br>But theres a caveat to me having that job: I have -zero- use for the bsddb module myself today. Whenever I update it it really is a donation of my time since I don't personally need the changes. A maintainer that has a vested interest in using the module would be a great thing. There are a couple crashing bugs that need fixing and a few more recent API additions that could be wrapped for sure.
<br><br>Volunteering Jesus? :)<br><br>-gps<br><br></div></div>