going forward with python-lounge

[Randall Leeds]

Something about python-lounge's db_config dictionary has never sat
right with me.
I'd kind of like to make use_config take the connection info directly
(maybe support kw args for auth in the future?)

But really, what I want to see is python-lounge move outside of the
lounge project and become a generic couchdb library in its own right.
There is no reason python-lounge should know about the shard map.
Moving the ShardMap class into smartproxy would remove smartproxy's
dependence on python-lounge, which is a dependency that has always
bothered me.

Are you using python-lounge? Why or why not?
Also, please be sure to report problems you have interacting with
lounge with your client library of choice. Lounge aims to be a fully
'compliant' couch server.

-Randall

[David Pratt]

Hi Randall. The meebo folks have generously shared lounge which is
pretty decent. I am using couchdb-python client and needed minor
changes for it to work. I have repackaged lounge for my own purposes
excluding python-lounge and its imports. I will be contributing bulk
docs to lounge some time in the near future once I have got something
finished. Time has been my enemy lately. Incidentally, I put the
ShardMap class in a utils module in my lounge package (since it is
also utilized by the nginx dumbproxy).

I would suggest you fork and/or contribute to consume python-lounge
the way you want. You could see whether meebo devs are content with
your modifications afterwards. If not, the lib is pretty small.
Repackaging is not a big deal if you wished to track python-lounge
development and maintain its versions on pypi (for yourself and others
to consume separately).

Regards,
David

> --
> To unsubscribe, reply using "remove me" as the subject.

[Kevin Ferguson]

David, what changes did you need to make to couchdb-python?  We'd like to try and make lounge 'just work' in as many situations as possible.

[Randall Leeds]

On Sun, Apr 4, 2010 at 15:46, David Pratt <fairwi...@gmail.com> wrote:
> I would suggest you fork and/or contribute to consume python-lounge the way
> you want. You could see whether meebo devs are content with your
> modifications afterwards. If not, the lib is pretty small. Repackaging is

Hehe. Kevin and I work at Meebo. We do have code reviews. I was
specifically reaching out to the community on this question as I try
to make lounge development more community driven and transparent.

[till]

On Sun, Apr 4, 2010 at 4:46 PM, David Pratt <fairwi...@gmail.com> wrote:
> Hi Randall.  The meebo folks have generously shared lounge which is pretty
> decent.   I am using couchdb-python client and needed minor changes for it
> to work. I have repackaged lounge for my own purposes excluding
> python-lounge and its imports. I will be contributing bulk docs to lounge
> some time in the near future once I have got something finished.

We have a large test setup right now and are looking to migrate 250
million docs to the lounge. Our obstacle are bulk docs right now, or
rather the lack of. :)

Till