fixed tuple unpacking error when adding new entries to lexicon.txt #30
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.
When adding new entries to vader_lexicon.txt, Unix text editors will add a newline to the end of files to comply with standards. The problem is that when nltk reads the entire file then vader splits the lines, the code reads an empty entry. When python attempts to unpack the line into a tuple, it crashes.
The resulting error looks something like the text I attached below.
I fixed the issue by striping a newline within the body of SentimentIntensityAnalzyer.make_lex_dict(). Nltk gives a single line of text when it reads the file, so rstrip just removes the very last newline.