On Jul 22, 2010, at 17:52, Bill Janssen wrote:
Andi Vajda wrote:
On Jul 22, 2010, at 2:09, Bill Janssen wrote:
Andi Vajda wrote:
Porting your stuff to 3.0 is thus highly recommended instead
of complaining about broken (my bad) long- deprecated APIs.
Hey, take 2.9.3 down, and announ
Andi Vajda wrote:
>
> On Jul 22, 2010, at 2:09, Bill Janssen wrote:
>
> > Andi Vajda wrote:
> >
> >> Porting your stuff to 3.0 is thus highly recommended instead
> >> of complaining about broken (my bad) long- deprecated APIs.
> >
> > Hey, take 2.9.3 down, and announce no further pylucene sup
On Jul 22, 2010, at 2:09, Bill Janssen wrote:
Andi Vajda wrote:
Porting your stuff to 3.0 is thus highly recommended instead
of complaining about broken (my bad) long- deprecated APIs.
Hey, take 2.9.3 down, and announce no further pylucene support for
2.x,
and I'll stop talking about i
Andi Vajda wrote:
> Porting your stuff to 3.0 is thus highly recommended instead
> of complaining about broken (my bad) long- deprecated APIs.
Hey, take 2.9.3 down, and announce no further pylucene support for 2.x,
and I'll stop talking about it.
Bill
On Jul 21, 2010, at 23:10, Bill Janssen wrote:
Andi Vajda wrote:
On Jul 21, 2010, at 19:59, Bill Janssen wrote:
Bill Janssen wrote:
What's crashing with PyLucene 2.9.3 is this code:
for field in x.getFields():
where "x" is an instance of org.apache.lucene.document.Document. I
c
> Presumably that's no longer the case with JCC 2.6. Probably should be
> updated to whatever the current version does. Or perhaps versioned and
> checked into the source tree.
It could be related to the --no-generics addition. Have you tried to
recompile PyLucene with the option "JCCFLAGS="?
C
On Jul 21, 2010, at 20:38, Bill Janssen wrote:
Bill Janssen wrote:
Bill Janssen wrote:
What's crashing with PyLucene 2.9.3 is this code:
for field in x.getFields():
where "x" is an instance of org.apache.lucene.document.Document.
I can
print x and it looks OK, but an attempt to
On Jul 21, 2010, at 19:59, Bill Janssen wrote:
Bill Janssen wrote:
What's crashing with PyLucene 2.9.3 is this code:
for field in x.getFields():
where "x" is an instance of org.apache.lucene.document.Document. I
can
print x and it looks OK, but an attempt to iterate over the list
On Jul 21, 2010, at 19:33, Bill Janssen wrote:
What's crashing with PyLucene 2.9.3 is this code:
for field in x.getFields():
where "x" is an instance of org.apache.lucene.document.Document. I
can
print x and it looks OK, but an attempt to iterate over the list of
fields seems broken.
Bill Janssen wrote:
> What's crashing with PyLucene 2.9.3 is this code:
>
> for field in x.getFields():
>
> where "x" is an instance of org.apache.lucene.document.Document. I can
> print x and it looks OK, but an attempt to iterate over the list of
> fields seems broken. Is this another
What's crashing with PyLucene 2.9.3 is this code:
for field in x.getFields():
where "x" is an instance of org.apache.lucene.document.Document. I can
print x and it looks OK, but an attempt to iterate over the list of
fields seems broken. Is this another iterator change?
Bill
Thread 14 Cr
On Jul 21, 2010, at 12:18 AM, Thomas Koch wrote:
> The question remains if it's feasible to support 2.x *and* 3.x - as Bill
> mentioned "... I'd like to make it work on both." - me too. I did fear that
> this makes things much more complicated and you end up with code "if
> lucene.VERSION.split('
On Wed, 21 Jul 2010, Thomas Koch wrote:
But I understand now that as long as you remove deprecated code from 2.9 it
*should* work with 2.9 and 3.0 as well! Right?
Correct.
e.g.
Hits search(Query query)
Is now deprecated as
"Hits will be removed in Lucene 3.0"
2.9 already supports
TopDocs
> ...
> I realize that PyLucene doesn't make that easy because it doesn't warn
> about deprecated API use.
>
[Thomas Koch] Well this is a general drawback in Python as interpreted
language I guess - wrong interfaces are only detected at runtime and are
thus harder to test (unless you describe the
On Jul 20, 2010, at 4:40, Bill Janssen wrote:
Looks like the combination of JCC 2.6 and Lucene 2.9.3 have made some
significant API changes. This is what I get with 2.9.3:
% python /u/python/uplib/indexing.py search /local/demo-repo/index
picasso
[...]
hits are (0 hits)
Traceback (most r
Looks like the combination of JCC 2.6 and Lucene 2.9.3 have made some
significant API changes. This is what I get with 2.9.3:
% python /u/python/uplib/indexing.py search /local/demo-repo/index picasso
[...]
hits are (0 hits)
Traceback (most recent call last):
File "/u/python/uplib/indexing.py"
16 matches
Mail list logo
