Hi Shawn,
On Tue, 13 Nov 2012, Shawn Grant wrote:
Hi Andi, I was just wondering if Pylucene is on its usual schedule to release
4-6 weeks after Lucene. I didn't see any discussion of it on the mailing
list or elsewhere. I'm looking forward to 4.0!
Normally, PyLucene is released a few days after a Lucene release but 4.0 has
seen so many API changes and removals that all tests and samples need to be
ported to the new API. Last week-end, I ported a few but lots remain to be.
If no one helps, it either means that no one cares enough or that everyone
is willing to be patient :-)
The PyLucene trunk svn repository is currently tracking the Lucene Core 4.x
branch and you're welcome to use it out of svn. In the ten or so unit tests
I ported so far, I didn't find any issues with PyLucene proper (or JCC). All
changes were due to the tests being out of date or using deprecated APIs now
removed. You might find that PyLucene out-of-trunk is quite usable.
If people want to help with porting PyLucene unit tests, the ones under its
'test' directory not yet ported, feel free to ask questions here.
The gist of it is:
- fix the imports (look at the first few tests for example,
alphabetically)
- fix the tests to pass by looking at the original Java tests for changes
as most of these tests were originally ported from Java Lucene.
Once you're familiar with the new APIs, porting the sample code in samples
and in LuceneInAction should fairly straightforward. It's just that there is
a lot to port.
Andi..
