Procedures for submitting patches to pybsddb
I have a patch (DBCursor.get_current_size(), returns size of data for current entry) which I'd like to submit. This involves changes to pybsddb cvs as well as python cvs, from what I can tell (for tests and docs in the pybsddb repo). While I have developer access to pybsddb, I don't have it for Python. Submitting patches for two different repositories seems cumbersome, so where should I add it? Python SF tracker? -- Itamar Shtull-Trauring http://itamarst.org/ Available for Python & Twisted consulting
On Sun, 2003-09-28 at 00:52, Itamar Shtull-Trauring wrote:
While I have developer access to pybsddb, I don't have it for Python. Submitting patches for two different repositories seems cumbersome, so where should I add it? Python SF tracker?
Yes, because the pybsddb project weaves the actual bsddb files from the Python project. pybsddb is now just a distutils/documentation shell project. -Barry
On Sun, Sep 28, 2003 at 12:52:52AM -0400, Itamar Shtull-Trauring wrote:
I have a patch (DBCursor.get_current_size(), returns size of data for current entry) which I'd like to submit. This involves changes to pybsddb cvs as well as python cvs, from what I can tell (for tests and docs in the pybsddb repo).
While I have developer access to pybsddb, I don't have it for Python. Submitting patches for two different repositories seems cumbersome, so where should I add it? Python SF tracker?
If you submit the patch to the python project there's less dependance on me to check it and commit it. I suggest just including the pybsddb repository diffs as a second file in the patch and email the pybsddb-users mailing list afterwards pointing to it. If a patch is submitted to pybsddb; i'll usually notice and do the right thing, but many less eyes watch that patch manager. The pybsddb-users email is a nice headsup because i read that low volume list more often than python-dev. -g
participants (3)
-
Barry Warsaw -
Gregory P. Smith -
Itamar Shtull-Trauring