Closed greebie closed 5 years ago
Okay. Will fix.
I knew you were going to say that about international(), but I just couldn't bear seeing it just be wrong and out there in the open for such a small change. Also, I knew that #42 was still in the issues, so the tracking is still available.
Latest commit should resolve all issues stated above.
I think that's a different issue which might be fixed more generally in another branch, especially if we look at making a module to cover the functions.
Essentially we have general madlibs and more specific madlibs and it's not always clear which is which. I don't think that it's that helpful to tell people to scroll up to change something. Let's look at the overall explanations / docs / comments together as a separate issue. (Maybe after receiving feedback from the datathon as well.)
OK. I still don't think
vals = [x[1] for x in tokens if x[0] not in STOP_WORDS] # Filter based on STOP_WORDS (above).
is clear? Filter what? Filter in? Filter out? Can you try to take a kick at the can to make it a bit more usable?
I think that's a different issue which might be fixed more generally in another branch, especially if we look at making a module to cover the functions.
No. That's in scope for this PR. Ian's suggestion makes sense. Can you update your PR to include that, and we can continue to iterate from there.
Now that I've been able to look at this more closely, I see your point. I have some follow-up work this morning, but will get this fixed in the afternoon.
This PR gives the user the options to use NLTK stopwords and/or add their own. This was a common demand from the datathon.
I also removed the International () function call because it is not doing what I originally thought it was doing.