Fix LookupError from nltk.pos_tag in Wordnet model #349
Conversation
This file contains hidden or 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
Author
|
Happy to adjust anything if needed. Thanks for reviewing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This fixes an issue where
nltk.pos_tag()internally triggers aLookupErrordue to attempting to load the non-existent resourceaveraged_perceptron_tagger_eng. The fix avoids this by directly usingPerceptronTagger()without thelang='eng'parameter, and re-instantiates it after downloading the tagger model if necessary. Verified in Google Colab, this resolves the common synonym augmentation crash encountered by many users when usingnlpaugwith WordNet-based augmenters. The change is backward-compatible with existing usage.