gregory p smith amuhkryptoorg 3408 jesus cea wrote said aim keep bsddb stdlib providing stable featureful module think keeping bsddb development inside python svn appropiate currently could change idea approach keeping pybssdb separate project sync python svn time time mainly take advantage buildbot architecture course able release python current bindings since python commit access seems sensible approach could frequent pybssdb releases let say every couple months without waiting full python release current approach makes sense also agree neals comments merging back python reasonable sized chunks good dont worry commit access ill initial pybsddb back python trunk merges get setup ive merged python trunk changes others made back pybsddb tree ps tried sign python contributor agreement sure current pybsddb license terms help welcomed current bsddb license first foremost python license read comments _bsddb file correctly believe could also call mit style license keep things simple write python license contributor form submit gps tue 05 aug 2008 201628 0800 pythondev bsddb3 buildbots trunk red