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:
[1
Jiang Fung Wong 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:
> build/_lucene/org/a
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).
N
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 pr
On Sat, Nov 19, 2011 at 5:12 PM, Andi Vajda wrote:
>
> 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.
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.InvalidArgsErro
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)
--> SIGSEGV?
IndexWriterConfig expects an analyzer as a 2nd argument... but I wou
On Sat, Nov 19, 2011 at 5:53 PM, Andi Vajda 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)
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 e
On Sat, 19 Nov 2011, Michael McCandless wrote:
On Sat, Nov 19, 2011 at 5:53 PM, Andi Vajda 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.
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. Th
On Sat, Nov 19, 2011 at 6:34 PM, Andi Vajda 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 o
12 matches
Mail list logo
