Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

konlpy & boilerpipe mutually creates exceptions #33

Open
e9t opened this issue Jul 17, 2015 · 1 comment
Open

konlpy & boilerpipe mutually creates exceptions #33

e9t opened this issue Jul 17, 2015 · 1 comment

Comments

@e9t
Copy link

e9t commented Jul 17, 2015

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 (konlpy/konlpy#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.

@e9t e9t changed the title konlpy, boilerpipe creates exceptions for each other konlpy & boilerpipe mutually creates exceptions Jul 17, 2015
@tuxdna
Copy link
Collaborator

tuxdna commented Sep 12, 2016

@e9t Can you check if this issue still happens? How replicate the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants