-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
stop_words assigned but not used? #639
Comments
Aside: the English |
Thanks. What's supposed to happen is the Agree about the English stop list. |
Re English stopwords: I'm currently in the process of reorganising the language data. Just posted an update here: #649 |
…messy, but it's better not to change too much until the language data loading can be properly refactored.
Put a band-aid on this for now. A more satisfying fix will come alongside the data reorganisation. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Maybe I'm being dense, but when I search the entire repo case-insensitively for
stop_words
, it looks like you're defining a list of stop words but never using it. Every match in the Sublime search below is an assignment; all you seem to do is defineSTOP_WORDS
constants inlanguage_data.py
files and then assign those constants to thestop_words
class property of aLanguage
'sDefaults
, without ever then reading from it:Does this list still have a purpose, or should it be culled? I thought I'd flag this up before any of you dutifully hunt down stop word lists for the new languages you're adding!
Apologies if there's some reason for this to exist that I'm missing.
The text was updated successfully, but these errors were encountered: