art the release process.
Thanks !
Andi..
Thomas
-Ursprüngliche Nachricht-
Von: Andi Vajda [mailto:va...@apache.org]
Gesendet: Donnerstag, 3. Mai 2012 20:14
An: pylucene-dev@lucene.apache.org
Betreff: Re: AW: AW: AW: AW: PyLucene use JCC shared object by default
...
I fixed your patch to use
> > As far as I understand
> > elem0 = jArray[0] -> yields python object
> >
> > elem0 = arrayList.get(0) -> yields wrapped Java object
> >
> > Not sure if that's intended. In that case the test should be fixed ,-)
>
> If the array is an array of object, then objects you get, including
instances o
On Thu, 3 May 2012, Thomas Koch wrote:
thanks for the fixes and cleanup! I've updated from SVN and wrote the unit
test. Runs withtout errors (Tracebacks etc.) now, however there may be
some slight type mismatch issue still: the comparison of objects retrieved
from JArray and ArrayList respect
-
Von: Andi Vajda [mailto:va...@apache.org]
Gesendet: Donnerstag, 3. Mai 2012 01:00
An: pylucene-dev@lucene.apache.org
Betreff: Re: AW: AW: AW: PyLucene use JCC shared object by default
Hi Thomas,
On Wed, 2 May 2012, Thomas Koch wrote:
could you download the patch from the link?
Yes, I
ests in 0.031s
FAILED (failures=4)
> -Ursprüngliche Nachricht-
> Von: Andi Vajda [mailto:va...@apache.org]
> Gesendet: Donnerstag, 3. Mai 2012 01:00
> An: pylucene-dev@lucene.apache.org
> Betreff: Re: AW: AW: AW: PyLucene use JCC shared object by default
>
>
> Hi Thom
helps...
Regards,
Thomas
-Ursprüngliche Nachricht-
Von: Andi Vajda [mailto:va...@apache.org]
Gesendet: Montag, 30. April 2012 19:32
An: pylucene-dev@lucene.apache.org
Betreff: Re: AW: AW: PyLucene use JCC shared object by default
On Mon, 30 Apr 2012, Thomas Koch wrote:
Dear Andi, I again had a loo
Sorry about that - you can find it here
http://db.tt/nhiCrgGU
Regards
Thomas
--
Am 30.04.2012 um 19:31 schrieb Andi Vajda :
>
> On Mon, 30 Apr 2012, Thomas Koch wrote:
>
>> Dear Andi, I again had a look at the patch I submitted recently and would
>> like to get back to it. An updated version
Hi Andi,
thanks for getting back on this issue.
> Lucene 3.6 just got released a few days ago. Apart from your patch, the
> PyLucene 3.6 release is ready. I'm about to go offline (email only) for a
> week.
> Let's revisit this patch then (first week of May). It's not blocking the
> release
> rig
