We're pulling it out in part because you're a committer :) Also we're
tracking the trunk of couchdb, so that probably means we'l be tracking
the trunk of the python package too and also hitting snags where the
package hasn't quite caught up.
Nothing really needs changing atm, but I find it useful to have it on
hand for debugging and any changes that we may want to push into it. I
did file one patch for better logging on the google code site:
http://code.google.com/p/couchdb-python/issues/detail?id=55
I also was thinking once it's cleaned up and sane, some of the wierd
orm that melkjug is growing in the couchdb package may be useful to
the couchdb orm thinger.
- Luke
On Feb 11, 2009, at 1:53 AM, Randall Leeds wrote:
Why are we bringing CouchDB Python in as source?
You realize I'm a committer, right?
Can you tell me what needs to be changed?
--
Archive:
http://www.openplans.org/projects/melkjug/lists/melkjug-development-list/archive/2009/02/1234362193248
To unsubscribe send an email with subject "unsubscribe" to
[email protected]. Please contact [email protected]
for questions.
