Kelly Peterson

This is indeed one of the conventions of current spaCy versions as you noted from [this GitHub issue](https://github.com/explosion/spaCy/issues/3608). So yes, there are a few ways to expose more of the...

@soldni I apologize. Sometimes I need to type something out before I realize my mistake. In this case, I previously read your documentation incorrectly. Specifically, I just looked at what...

@DSLituiev As a part of medspacy, we have started our own fork of QuickUMLS. In this fork, we support spacy v3.x and we have addressed this issue with version 2.5...

Sorry for the close/reopen but I was confused why this shows 4 commits instead of 1. The overall diff looks right, but please advise if there's a better way I...

That sounds great @soldni. I understand the limitations of bandwidth since I initially planned to submit these pull requests back in October 2019 and then lots of things got in...

Any update on this pull request? And perhaps bumping the version number in PyPi? We're about to do a major release of medspacy (https://github.com/medspacy/medspacy) and we wanted to include QuickUMLS...

OK, this has been made available now with medspacy 1.0.0. But I'd like to make sure that my terminology is clear. Spacy still does not allow overlapping entities. At least...

I finally have a PR ready for this one. I did not follow this recommendation exactly, but I think my approach is a bit simpler and easy to maintain given...

This has now been resolved in medspacy 1.0.0. All QuickUMLS arguments should now be supported when using a `config` dictionary when creating the component with `add_pipe()`.

I was not very clear in my intent on this one. While we now currently are able to run `pip install medspacy`, I want to set up CI that this...