Hi, currently, pylucene gets a SIGSEGV as soon you call a Java method without previously initializing the JVM (or attaching the current thread).
I know the root cause (no initialization) is a programmer error and pylucene has its reasons to not initialize the JVM automatically. But I think pylucene should not crash but just throw a JavaError which can be catched as every other Python exception. I experienced some crashes because my thread configuration was wrong and it was not too easy finding the cause. Maybe this is already fixed in SVN? I'm using JCC 1.9 and PyLucene 2.3.2.1 on CentOS 5 (i386) together with OpenJDK (1.6.0.0-0.7.b08.el5.2). fs
uninitialized_lucene.py
Description: application/crossover-py
_______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
