-
Notifications
You must be signed in to change notification settings - Fork 32
seperate_words function based on \W+ re instead? #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
@fabianvf bump |
@fabianvf thoughts on this? |
Honestly I'm not sure, does it make a difference? Wonder if there are any edge cases related to punctuation or something that will bite us. |
It'll be important for nonwestern languages.
…On Aug 31, 2017 4:18 PM, "Fabian von Feilitzsch" ***@***.***> wrote:
Honestly I'm not sure, does it make a difference? Wonder if there are any
edge cases related to punctuation or something that will bite us.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AShd7CGb6Mvox5WWWtd2GjTIZhujfB7rks5sdxT8gaJpZM4OwesY>
.
|
@fabianvf Also doing it that way is faster, easier to understand and more maintainable/pythonic |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@fabianvf Is it my imagination or could we replace the entire separate_words function better with a \W+ or \W regex instead?
The text was updated successfully, but these errors were encountered: