use rapidfuzz instead of fuzzywuzzy #655
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: maxbachmann <[email protected]>
ekmb
approved these changes
May 22, 2020
|
@maxbachmann thank you for the PR. |
dcurran90
pushed a commit
to dcurran90/NeMo
that referenced
this pull request
Oct 15, 2024
Now supports a diff from a specific commit (in addition to a branch or HEAD) Fixes NVIDIA#654 Signed-off-by: Derek Higgins <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FuzzyWuzzy and python-Levenshtein are GPLv2 or later licensed which requires to license projects that use them to be GPL Licensed aswell.
For this reason this Pullrequest replaces FuzzyWuzzy with RapidFuzz (I am the author) which is implementing the same algorithms but is based on a old version of fuzzywuzzy that was MIT Licensed.
Rapidfuzz is: