You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pylucene-dev@lucene.apache.org by Andi Vajda <va...@apache.org> on 2010/07/12 21:38:31 UTC
JCC and PyLucene ported to Python 3.0
Today, I ported JCC and PyLucene (trunk) to Python 3.1.2 on Mac OS X 10.6.
All unit tests and Lucene in Action samples pass. 2to3 did wonders. So did
the docs for all the manual C code changes.
If you'd like to check it out:
- install Python 3.1.2
- install the latest distribute
- check out http://svn.apache.org/repos/asf/lucene/pylucene/branches/python_3/
Bugs, comments, etc.. welcome !
Andi..
Re: JCC and PyLucene ported to Python 3.0
Posted by Andi Vajda <va...@apache.org>.
On Wed, 14 Jul 2010, Aric Coady wrote:
> Thanks, great work. I ran into minor build issues (also using Python
> 3.1.2 on Mac OS X 10.6):
>
> BUILD FAILED
> pylucene3/lucene-modules-4.0/build.xml:31: The following error occurred while executing this line:
> pylucene3/lucene-modules-4.0/analysis/build.xml:31: The following error occurred while executing this line:
> pylucene3/lucene-modules-4.0/analysis/common/build.xml:30: Cannot find ../../../lucene/contrib/contrib-build.xml imported from pylucene3/lucene-modules-4.0/analysis/common/build.xml
>
> BUILD FAILED
> pylucene3/lucene-modules-4.0/build.xml:31: The following error occurred while executing this line:
> pylucene3/lucene-modules-4.0/analysis/build.xml:35: The following error occurred while executing this line:
> pylucene3/lucene-modules-4.0/analysis/icu/build.xml:42: The following error occurred while executing this line:
> pylucene3/lucene/contrib/contrib-build.xml:134: pylucene3/modules/analysis/common/src/java not found.
>
> The directories "lucene-java-4.0" and "lucene-modules-4.0" are created,
> but looks like the paths "lucene" and "modules" are expected. After
> making some links everything built fine and all tests passed.
Yes, you need to setup links to these directories in the PyLucene directory
as modules and core cross-reference each other. The Lucene trunk build is a
bit in flux at the moment.
lrwxr-xr-x 1 vajda admin 15 May 13 15:24 lucene -> lucene-java-4.0
lrwxr-xr-x 1 vajda admin 18 May 17 13:43 modules -> lucene-modules-4.0
> Would you consider tracking branch_3x (3.1) instead of trunk (4.0)? 4.0
> is not backwards compatible and in flux. I can't really test it with my
> own project further because the changes in 4.0 are so extensive; I assume
> 3.1 will be the next lucene release.
lucene's branch_3x is tracked by pylucene's branch_3x:
http://svn.apache.org/repos/asf/lucene/pylucene/branches/branch_3x/
If you'd like to build PyLucene 3.x with Python 3, you can use the JCC 2.6
for python 3 from the python_3 branch:
http://svn.apache.org/repos/asf/lucene/pylucene/branches/python_3/jcc/
The 'only' issue should be that unit tests and samples are going to fail
since they're not compatible with Python 3 on the branch_3x branch.
I still expect PyLucene 3.x it to build and run fine with the Python 3 JCC
2.6, though, but I haven't actually tried it.
Andi..
>
> On Jul 12, 2010, at 12:38 PM, Andi Vajda wrote:
>
>>
>> Today, I ported JCC and PyLucene (trunk) to Python 3.1.2 on Mac OS X 10.6.
>> All unit tests and Lucene in Action samples pass. 2to3 did wonders. So did the docs for all the manual C code changes.
>>
>> If you'd like to check it out:
>> - install Python 3.1.2
>> - install the latest distribute
>> - check out http://svn.apache.org/repos/asf/lucene/pylucene/branches/python_3/
>>
>> Bugs, comments, etc.. welcome !
>>
>> Andi..
>
Re: JCC and PyLucene ported to Python 3.0
Posted by Aric Coady <ar...@gmail.com>.
Thanks, great work. I ran into minor build issues (also using Python 3.1.2 on Mac OS X 10.6):
BUILD FAILED
pylucene3/lucene-modules-4.0/build.xml:31: The following error occurred while executing this line:
pylucene3/lucene-modules-4.0/analysis/build.xml:31: The following error occurred while executing this line:
pylucene3/lucene-modules-4.0/analysis/common/build.xml:30: Cannot find ../../../lucene/contrib/contrib-build.xml imported from pylucene3/lucene-modules-4.0/analysis/common/build.xml
BUILD FAILED
pylucene3/lucene-modules-4.0/build.xml:31: The following error occurred while executing this line:
pylucene3/lucene-modules-4.0/analysis/build.xml:35: The following error occurred while executing this line:
pylucene3/lucene-modules-4.0/analysis/icu/build.xml:42: The following error occurred while executing this line:
pylucene3/lucene/contrib/contrib-build.xml:134: pylucene3/modules/analysis/common/src/java not found.
The directories "lucene-java-4.0" and "lucene-modules-4.0" are created, but looks like the paths "lucene" and "modules" are expected. After making some links everything built fine and all tests passed.
Would you consider tracking branch_3x (3.1) instead of trunk (4.0)? 4.0 is not backwards compatible and in flux. I can't really test it with my own project further because the changes in 4.0 are so extensive; I assume 3.1 will be the next lucene release.
On Jul 12, 2010, at 12:38 PM, Andi Vajda wrote:
>
> Today, I ported JCC and PyLucene (trunk) to Python 3.1.2 on Mac OS X 10.6.
> All unit tests and Lucene in Action samples pass. 2to3 did wonders. So did the docs for all the manual C code changes.
>
> If you'd like to check it out:
> - install Python 3.1.2
> - install the latest distribute
> - check out http://svn.apache.org/repos/asf/lucene/pylucene/branches/python_3/
>
> Bugs, comments, etc.. welcome !
>
> Andi..