Re: Plans for a new Solr Python library

2008-03-25 Thread Mike Klaas
On 24-Mar-08, at 3:32 AM, Leonardo Santagada wrote: On 24/03/2008, at 04:39, Christian Vogler wrote: On Monday 24 March 2008 01:01:59 Leonardo Santagada wrote: I have done some modifications on the solr python client[1], and though we kept the same license and my work could be put back in so

Re: Plans for a new Solr Python library

2008-03-25 Thread David Pratt
Have you got a link to the new project. Many thanks. David Leonardo Santagada wrote: On 24/03/2008, at 15:34, Yonik Seeley wrote: On Mon, Mar 24, 2008 at 12:27 PM, Ed Summers <[EMAIL PROTECTED]> wrote: On Mon, Mar 24, 2008 at 12:13 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote: AFAIK, no one h

Re: Plans for a new Solr Python library

2008-03-24 Thread Leonardo Santagada
On 24/03/2008, at 15:34, Yonik Seeley wrote: On Mon, Mar 24, 2008 at 12:27 PM, Ed Summers <[EMAIL PROTECTED]> wrote: On Mon, Mar 24, 2008 at 12:13 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote: AFAIK, no one has fixed the outstanding bugs and indicated it was ready to be committed. What is the

Re: Plans for a new Solr Python library

2008-03-24 Thread Yonik Seeley
On Mon, Mar 24, 2008 at 12:27 PM, Ed Summers <[EMAIL PROTECTED]> wrote: > On Mon, Mar 24, 2008 at 12:13 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote: > > AFAIK, no one has fixed the outstanding bugs and indicated it was > > ready to be committed. > > What is the preferred approach to fixing bugs

Re: Plans for a new Solr Python library

2008-03-24 Thread Ed Summers
On Mon, Mar 24, 2008 at 12:13 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote: > AFAIK, no one has fixed the outstanding bugs and indicated it was > ready to be committed. What is the preferred approach to fixing bugs in patches? Attaching new patches? //Ed

Re: Plans for a new Solr Python library

2008-03-24 Thread Yonik Seeley
On Mon, Mar 24, 2008 at 6:32 AM, Leonardo Santagada <[EMAIL PROTECTED]> wrote: > Thanks, I think most of the stuff that I wanted to do is there... I > will take a closer look and if there is omething missing I will add to > that. Why is this on the issue tracker and was not commited to the svn?

Re: off list: Plans for a new Solr Python library

2008-03-24 Thread Leonardo Santagada
On 24/03/2008, at 10:15, Christian Vogler wrote: Ok, so, let's get started. I made a few modifications to SOLR-216 that fix some unicode and timezone conversion issues, and I can upload them wherever we want to host the project. There is at an outstanding XML unicode bug that was discussed

Re: Plans for a new Solr Python library

2008-03-24 Thread Leonardo Santagada
On 24/03/2008, at 09:11, Ed Summers wrote: On Mon, Mar 24, 2008 at 6:32 AM, Leonardo Santagada <[EMAIL PROTECTED]> wrote: Thanks, I think most of the stuff that I wanted to do is there... I will take a closer look and if there is omething missing I will add to that. Why is this on the issue tr

Re: Plans for a new Solr Python library

2008-03-24 Thread Ed Summers
On Mon, Mar 24, 2008 at 6:32 AM, Leonardo Santagada <[EMAIL PROTECTED]> wrote: > Thanks, I think most of the stuff that I wanted to do is there... I > will take a closer look and if there is omething missing I will add to > that. Why is this on the issue tracker and was not commited to the svn?

Re: Plans for a new Solr Python library

2008-03-24 Thread Leonardo Santagada
On 24/03/2008, at 04:39, Christian Vogler wrote: On Monday 24 March 2008 01:01:59 Leonardo Santagada wrote: I have done some modifications on the solr python client[1], and though we kept the same license and my work could be put back in solr I think if there are more people interested we could

Re: Plans for a new Solr Python library

2008-03-24 Thread Christian Vogler
On Monday 24 March 2008 01:01:59 Leonardo Santagada wrote: > I have done some modifications on the solr python client[1], and > though we kept the same license and my work could be put back in solr > I think if there are more people interested we could improve the > module a lot. Have you taken a

Plans for a new Solr Python library

2008-03-23 Thread Leonardo Santagada
I have done some modifications on the solr python client[1], and though we kept the same license and my work could be put back in solr I think if there are more people interested we could improve the module a lot. As it is now it is looks to much unpythonic. Another BIG problem is using t