Correct unicode equality issue in python 2.7 #222
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
gunthercox
force-pushed
the
unicode
branch
2 times, most recently
from
dc38a42 to
f5e3030
Compare
gunthercox
force-pushed
the
unicode
branch
11 times, most recently
from
92d43c5 to
2bf3faa
Compare
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.
Closes #215
Related seatgeek/fuzzywuzzy#129
This corrects a few of the unicode string errors that were occurring in ChatterBot. The main issue was that a redundant check for an exact string match was being made. This has been removed and a more unicode-friendly implementation of the fuzzy matching functionality for statements is now being used.