-
Notifications
You must be signed in to change notification settings - Fork 95
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
Feature request: include setup.py #18
Comments
Joshua, Thanks for the suggestion! I am a bit time constrained at the moment, but I plan to look into this in the future. -Luca |
I was thinking about this too and I might try to get some time to add a setup.py and test this. I've been building something up using QuickUMLS and I'd love for it to be an easier dependency install for the pipeline I'm building. With any luck, I might have a pull request in a week or two. |
Kelly, I would be delighted if you can take up the mantle for that -- I'm currently a bit of capacity. Best, |
Excellent. I made some progress yesterday with both this and simstring. I'll keep you apprised of my progress. If this works out, we'll need to briefly discuss registering the package(s) and version numbering. |
I finally have an update on this: I have a branch that is pip installable. I am not 100% ready to make a full announcement yet, but you can already install QuickUMLS via |
@soldni Thanks for this awesome update! I successfully installed it with Python3, but get an error when using Python2. To reproduce:
There's quite a long stacktrace, but it ends with
|
Since Python 2.x is retiring in 6 months, I would propose that this may not warrant attention but instead users work within Python 3.x: |
This is excellent news @soldni . If you could benefit from any testing, let me know. I still need to share the changes I've made to wrap QuickUMLS as a true spacy component in modular pipelines, but I wonder if I should do this after hearing what kind of announcement you have planned. |
@sandertan as mentioned by Kelly, python 2 deprecation is imminent, so I was planning to drop support starting with version 1.3. @burgersmoke That would be awesome -- I hope the changes I'm making (mostly related to packaging and squashing relative imports) will not cause any major headache when rebasing. I am currently testing for MacOS (and maybe Windows? compatibility); other than that, we should be good to go. |
Testing was successful on macOS and UNIX. Merged! |
Would be nice to make this pip installable.
Thanks.
The text was updated successfully, but these errors were encountered: