[Impact]
jcc/__init__.py uses _jcc without directly importing importing it
this can cause import errors
this breaks e.g. the pylucene build in precise, see 935380
[Fix]
add to the __init__.py
from jcc import _jcc
as is done in quantal
[TEST CASE]
I have not managed to fine a simple testcase, so for now the pylucene build is the testcase
apt-get --compile pylucene
you should _not_ get this type of error:
File "/usr/lib/python2.7/dist-packages/jcc/__init__.py", line 37, in <module>
_jcc.CLASSPATH = CLASSPATH
NameError: name '_jcc' is not defined
[Regression potential]
low just a simple add of an import, it is already applied in quantal
[Impact]
jcc/__init__.py uses _jcc without directly importing importing it
this can cause import errors
this breaks e.g. the pylucene build in precise, see 935380
[Fix]
add to the __init__.py
from jcc import _jcc
as is done in quantal
[TEST CASE]
I have not managed to fine a simple testcase, so for now the pylucene build is the testcase
apt-get --compile pylucene
you should _not_ get this type of error: python2. 7/dist- packages/ jcc/__init_ _.py", line 37, in <module>
File "/usr/lib/
_jcc.CLASSPATH = CLASSPATH
NameError: name '_jcc' is not defined
[Regression potential]
low just a simple add of an import, it is already applied in quantal