On Wed, 6 Apr 2011, Bill Janssen wrote:
Andi Vajda <va...@apache.org> wrote:
On Wed, 6 Apr 2011, Bill Janssen wrote:
Andi Vajda <va...@apache.org> wrote:
Unless I'm missing something here, you've got two options before you
break your users:
1. fix your code before you ship it to them
Unfortunately, the code is out there for building, and the instructions,
also already out there, say, "PyLucene 2.4 to 3.X". I should be more
careful :-).
Given that APIs changed quite a bit between 2.x and 3.0 and that 2.x
deprecated APIs are removed from 3.1+ (unless I'm confused about
Lucene's deprecation policy (*)), your statement is a bit optimistic.
My Python code looks for the differences and handles it. Of course, it
can't do that for the future :-).
Is there some ABI version # that I should be checking, instead?
There are two versions available from the lucene module:
>>> import lucene
>>> [(v, lucene.__dict__[v]) for v in dir(lucene) if 'VERSION' in v]
[('JCC_VERSION', '2.8'), ('VERSION', '3.1.0')]
There is also the lucene.Version object.
Andi..
