2 ms·
Former fuzzywuzzy maintainer here. We relicensed fuzzywuzzy mostly because I am not a lawyer and really just wanted to stop having the same argument with the s
by josegonzalez 7y ago
Former fuzzywuzzy maintainer here.
We relicensed fuzzywuzzy mostly because I am not a lawyer and really just wanted to stop having the same argument with the same three people about whether what we were doing was legal. I actually think that we were violating the license by not including the license header on the included file, but were fine with the rest of the project being MIT, but again, not a lawyer, and the emails from the same ~3 people were becoming quite annoying.
Link here: https://github.com/seatgeek/fuzzywuzzy/issues/130 https://github.com/seatgeek/fuzzywuzzy/issues/130
That said, if their interpretation is right, then unless you clean-roomed the reimplementation, that derivative is also GPL.
Again, not a conversation I personally care for, and I no longer work for SeatGeek so it's no longer really on me :)
- maxbachmann 7y agoThats why I based it on a version before python-Levenshtein was even added to the project. The Levensthein part is just the normal levenshtein stuff that is a standard task at university I suppose, so it was definetly faster to implement this on my own instead of reading ugly C code. From my tests it is about as fast as the one used by python-Levenshtein (a little bit slower), but therefore I can read it ...