Tal Einat

Results 54 comments of Tal Einat

ValueError: end_index must be non-negative (again)

@jtlz2, I've started working on this. It seems like a problem with the native (C) extensions. In the meantime, you may install fuzzysearch without the native extensions by fetching a...

ValueError: end_index must be non-negative (again)

@jtlz2, I've fixed what appears to be the source of this issue. The fix is available in version 0.7.3 which I've just released. Please let me know if it resolves...

ValueError: end_index must be non-negative (again)

> Still get the same problem in 0.7.3 :\ ☹️ This seems to be related to the Anaconda distribution somehow, as it only appears to happen with it, but not...

Match exceeds max_l_dist when max_substitutions=0 is set

Thanks for the report @Stonatus, that looks like a bug!

Function find_near_matches is alternating results for the same situation

Hi Cristiano, thanks for this report! That is indeed very strange. I have been able to reproduce this locally using your script; many thanks for that! I'll look into this.

Unexpected behavior with only insertions allowed

Hi @artemuk, Thank you for such a clear and thorough description of the issue! fuzzysearch uses the opposite meaning of what insertion/deletion means: It defines them relative to the searched...

find_near_matches() uses substitution for distance calculation even if max_substitutions=0 is set.

Hey @Stonatus, This is currently the intended behavior, yes. The "dist" attribute of matches describes the Levenstein / edit distance, which is indeed 5 in this case. I can see...

Collect test coverage information for C and Cython code

For Cython code, see: http://blog.behnel.de/posts/coverage-analysis-for-cython-modules.html

Near matches get lost with increasing values of max_l_dist

Hi @davidefiocco, apologies for the late response. Yes, this is currently the intended behavior. The reason is that once the maximum distance is equal to (or greater than) the length...

add copying to list of license file names

A few lines above in the same list, there is already `"copy(left|right|ing)"`, which should match "copying". If that's broken, it should be fixed. In any case, adding "copying" to this...