Hi @misja.
I'm the maintainer of konlpy, a Korean NLP package for Python.
konlpy has recently been issued that using konlpy with python-boilerpipe creates exceptions (https://github.com/konlpy/konlpy/issues/66), and I figured it was because both packages use JPype1.
Specifically, boilerpipe inits jvm on import while konlpy inits jvm on class method calls, so the reported case errored on konlpy, because konlpy did not have classpaths that it needed. (On the other hand, if you run konlpy, and then attempt to import boilerpipe, boilerpipe will have the exeception.)
I saw on the project README that you no longer wanted to maintain python-boilerpipe, but was wondering if we could discuss how this problem could be easily fixed. Then maybe I can create a patch for both libraries. Thanks.
Hi @misja. I'm the maintainer of konlpy, a Korean NLP package for Python.
konlpy has recently been issued that using konlpy with python-boilerpipe creates exceptions (https://github.com/konlpy/konlpy/issues/66), and I figured it was because both packages use JPype1. Specifically, boilerpipe inits jvm on import while konlpy inits jvm on class method calls, so the reported case errored on konlpy, because konlpy did not have classpaths that it needed. (On the other hand, if you run konlpy, and then attempt to import boilerpipe, boilerpipe will have the exeception.)
I saw on the project README that you no longer wanted to maintain python-boilerpipe, but was wondering if we could discuss how this problem could be easily fixed. Then maybe I can create a patch for both libraries. Thanks.