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

Doesn't work with Pypy #61

Closed
polm opened this issue Feb 8, 2021 · 2 comments
Closed

Doesn't work with Pypy #61

polm opened this issue Feb 8, 2021 · 2 comments

Comments

@polm
Copy link
Collaborator

polm commented Feb 8, 2021

This is a followup to the below issue.

taku910/mecab#65

I confirmed that mecab-python3 doesn't work with Pypy. This seems to be an issue with SWIG, and it is not clear how easy it is to resolve.

However, fugashi just works with pypy, so I recommend using that.

https://github.com/polm/fugashi

Given that this is a SWIG issue of unclear complexity, and that fugashi just works, I am not interested in working on supporting Pypy. On the other hand, if there were a PR for support and it wasn't too complex I would be open to accepting it.

@polm
Copy link
Collaborator Author

polm commented Feb 9, 2021

Going to close this because I'm not working on it, but it can be useful to refer to in the future.

@polm polm closed this as completed Feb 9, 2021
@polm
Copy link
Collaborator Author

polm commented Feb 22, 2021

This suggests that with SWIG 4.0+ things should work with Pypy. However we're already using that version of SWIG so not sure what the issue is.

https://stackoverflow.com/questions/66096949/getting-gcc-failed-with-exit-status-1-when-trying-to-install-mecab-with-pypy/66226143#66226143

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

1 participant