possible JCC bug when slicing a JArray?

2011-11-19 Thread Michael McCandless
If I run this: import lucene import types arr = lucene.JArray(types.IntType)([1, 2, 3, 4]) it makes a length 4 int array, initialized with 1, 2, 3, 4. But then if I try to slice this array like this: print arr[0:] it prints: [1, 2, 3] but I think it should print:

Re: pylucene compilation error - reserved keywords

2011-11-19 Thread Bill Janssen
Jiang Fung Wong jiangfung.w...@jamiq.com wrote: I tried to compile pylucene on ArchLinux. JCC compilation was fine. When I tried to make. I got this error: In file included from build/_lucene/org/apace/lucene/util/mutable/MutableValueFloat.h:4:0, from build/_lucene/__wrap01__.cpp:17795:

SIGSEGV if I give wrong args to IndexWriterConfig ctor

2011-11-19 Thread Michael McCandless
Does anyone else see this? import lucene lucene.initVM() lucene.IndexWriterConfig(lucene.Version.LUCENE_34) -- SIGSEGV? IndexWriterConfig expects an analyzer as a 2nd argument... but I would expect a nice lucene.InvalidArgsError instead (that's what I hit if I pass no args to IWC).

Re: possible JCC bug when slicing a JArray?

2011-11-19 Thread Andi Vajda
Hi Mike, On Sat, 19 Nov 2011, Michael McCandless wrote: If I run this: import lucene import types arr = lucene.JArray(types.IntType)([1, 2, 3, 4]) it makes a length 4 int array, initialized with 1, 2, 3, 4. But then if I try to slice this array like this: print arr[0:] it

Re: SIGSEGV if I give wrong args to IndexWriterConfig ctor

2011-11-19 Thread Andi Vajda
Hi Mike, On Sat, 19 Nov 2011, Michael McCandless wrote: Does anyone else see this? import lucene lucene.initVM() lucene.IndexWriterConfig(lucene.Version.LUCENE_34) -- SIGSEGV? IndexWriterConfig expects an analyzer as a 2nd argument... but I would expect a nice lucene.InvalidArgsError

Re: SIGSEGV if I give wrong args to IndexWriterConfig ctor

2011-11-19 Thread Michael McCandless
On Sat, Nov 19, 2011 at 5:53 PM, Andi Vajda va...@apache.org wrote: On Sat, 19 Nov 2011, Andi Vajda wrote: Hi Mike, On Sat, 19 Nov 2011, Michael McCandless wrote: Does anyone else see this?  import lucene  lucene.initVM()  lucene.IndexWriterConfig(lucene.Version.LUCENE_34) --

Re: SIGSEGV if I give wrong args to IndexWriterConfig ctor

2011-11-19 Thread Andi Vajda
On Sat, 19 Nov 2011, Michael McCandless wrote: I need to take a closer look about what's different with this class. Strange... As long as I pass the analyzer as the 2nd arg (as I'm supposed to!) everything works fine; it's only if I leave off that 2nd arg that I hit the SEGV. Wow, that's

Re: SIGSEGV if I give wrong args to IndexWriterConfig ctor

2011-11-19 Thread Andi Vajda
On Sat, 19 Nov 2011, Michael McCandless wrote: On Sat, Nov 19, 2011 at 5:53 PM, Andi Vajda va...@apache.org wrote: On Sat, 19 Nov 2011, Andi Vajda wrote: Hi Mike, On Sat, 19 Nov 2011, Michael McCandless wrote: Does anyone else see this?  import lucene  lucene.initVM()  

Re: SIGSEGV if I give wrong args to IndexWriterConfig ctor

2011-11-19 Thread Andi Vajda
On Sat, 19 Nov 2011, Andi Vajda wrote: I need to take a closer look about what's different with this class. Strange... As long as I pass the analyzer as the 2nd arg (as I'm supposed to!) everything works fine; it's only if I leave off that 2nd arg that I hit the SEGV. Wow, you're right.

Re: SIGSEGV if I give wrong args to IndexWriterConfig ctor

2011-11-19 Thread Michael McCandless
On Sat, Nov 19, 2011 at 6:34 PM, Andi Vajda va...@apache.org wrote: On Sat, 19 Nov 2011, Andi Vajda wrote: I need to take a closer look about what's different with this class. Strange... As long as I pass the analyzer as the 2nd arg (as I'm supposed to!) everything works fine; it's only