Don't fail if nltk downloads don't work#33
Open
ysgit wants to merge 1 commit into
Open
Conversation
3 similar comments
Author
|
hey @csurfer did you get the chance to take a look at this? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
hi @csurfer, thanks for your work here!
I found I had to make this change in order to be able to be able to install the package as part of a serverless app to deploy on AWS lambda. In that context it doesn't really make sense to force download the NLTK data as part of the install of your package. In fact, the install failed because it didn't have access to nlltk at build time.