Skip to content
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

Is every NLTK data item necessary? #96

Open
g-simmons opened this issue May 7, 2021 · 0 comments
Open

Is every NLTK data item necessary? #96

g-simmons opened this issue May 7, 2021 · 0 comments

Comments

@g-simmons
Copy link

Hi all,

README has python -m nltk.downloader all

grep for nltk gives:

./lexmapr/predefined_resources/README.txt:import nltk
./lexmapr/predefined_resources/README.txt:from nltk.tokenize import sent_tokenize, word_tokenize
./lexmapr/predefined_resources/README.txt:from nltk import pos_tag, ne_chunk
./lexmapr/pipeline_classification.py:from nltk import word_tokenize
./lexmapr/pipeline.py:from nltk.tokenize import word_tokenize
./lexmapr/pipeline_resources.py:from nltk import word_tokenize
./lexmapr/pipeline_helpers.py:from nltk.tokenize import word_tokenize
./lexmapr/pipeline_helpers.py:from nltk.tokenize.treebank import TreebankWordDetokenizer
./lexmapr/pipeline_helpers.py:from nltk import pos_tag

Looks like you are using less than the majority of the ~100 data items provided by NLTK.

Would be nice to have in the README only the nltk data items that are necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant