[chandler-dev] chandlerdb and pylucene-2.4.1-1

[Jacob Floyd]

> That part of the Lucene store extensions needs to be reworked.
> The changes should be minimal, look at the svn history of PyLucene's
> test_PythonDirectory.py.

That seems to have been just the ticket I needed. Based on the various changes visible in svn, I made a patch for chandlerdb/persistence/LuceneContainer.py which is attached (I hope that's ok on this list, if not let me know, and I'll post it some other way) It seems to work for me, all the tests apparently pass, but please do a sanity check on what I changed.

> But, to do this properly, one needs to take on the task of upgrading
> PyLucene in the chandler build.
>
> Given, at least, that no new functionality is introduced by this
> upgrade that chandler lacks or desires, I don't think you'll get much
> interest in it.

ok. Well we'll see what happens with this patch then. Thanks for looking it over.

Thank you,
Jacob Floyd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 271 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20090411/57bbf92c/attachment.pgp 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: LuceneContainer.py.diff
Type: application/octet-stream
Size: 2167 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20090411/57bbf92c/attachment.obj