On Thu, 3 Nov 2011, A. Heifets wrote:
I got the build working by changing the import line in
/usr/lib64/python2.4/site-packages/jcc/__init__.py from
import os, sys
to
import os, sys, _jcc
That's unexpected. JCC should get installed as an egg. For example, on my
system, its installati
I got the build working by changing the import line in
/usr/lib64/python2.4/site-packages/jcc/__init__.py from
import os, sys
to
import os, sys, _jcc
> That's unexpected. JCC should get installed as an egg. For example, on my
> system, its installation dir looks like:
> .../lib/python2.
On Thu, 3 Nov 2011, A. Heifets wrote:
Ok. Why are you using such an old version of Python?
We have dependencies elsewhere in the system that lock us into 2.4
Not that I think that's the problem - just curious.
Any idea what the problem is? Or what additional diagnostics I can try?
You sa
> Ok. Why are you using such an old version of Python?
We have dependencies elsewhere in the system that lock us into 2.4
> Not that I think that's the problem - just curious.
Any idea what the problem is? Or what additional diagnostics I can try?
--
A. Heifets
http://www.cs.toronto.edu/~aheife
Sorry about that. I'm using the JCC in the
pylucene-3.4.0-1-src.tar.gz distribution downloaded on 2 Nov 2011.
On Thu, Nov 3, 2011 at 1:05 AM, Andi Vajda wrote:
> On Nov 2, 2011, at 17:14, "A. Heifets" wrote:
>> Hello PyLuceners,
>>
>> The PyLucene make command is failing with the following err
On Nov 2, 2011, at 17:14, "A. Heifets" wrote:
> Hello PyLuceners,
>
> The PyLucene make command is failing with the following error:
> Traceback (most recent call last):
> File "/usr/lib64/python2.4/site-packages/jcc/__init__.py", line 37, in ?
>_jcc.CLASSPATH = CLASSPATH
> NameError: name
