Adding language support to GetStreamFilter in api.py. Also added the example for that. - #401

Current coverage is 74.20% (diff: 0.00%)

Merging #401 into master will decrease coverage by 0.07%

@@             master       #401   diff @@
==========================================
  Files             8          8          
  Lines          1971       1973     +2   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits           1464       1464          
- Misses          507        509     +2   
  Partials          0          0          

Powered by Codecov. Last update d3eb170...2b25d70

Looks pretty good! A couple things I'd like to see:

• Could you update doc/changelog.rst to note the change?
• Since it's only a few lines different in track_users.py, it may make sense to incorporate the changes on lines 20, 57, & 71 into the existing file. That way if we have to update the examples, we just make changes in one place.

Let me know what you think on # 2.

(Don't worry about the code coverage thing - that function isn't tested yet anyway.)

Looks great! Thanks for your help! @bear you good with this?

Reviewed 2 of 3 files at r2.
Review status: 2 of 3 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

twitter/api.py, line 4455 at r2 (raw file):

                        track=None,
                        locations=None,
                        languages=None,

my only quibble is that the new parameter be added to the end because we are doing this in a point release.

if we add it into the middle of the parameter list then we break anyone who doesn't use named parameters in their calls.

Comments from Reviewable

Crap, I did the same thing with PostStatus in #394

@jeremylow ugh, sorry for not catching that! the benefit of smaller sized PRs

Yep. I'll fix it on develop.

Speaking of develop, I just noticed this is going into the master branch, so I switched it to get integrated with the rest of the changes for 3.2.

with that param change i'm +1 on merging - nicely done!

Awesome. Merged! Thanks @chaitanya0411 and congrats on your first PR!

Thanks guys ! It was a good experience !
I hope there are more PR to come from me...
Also, as mentioned at https://python-twitter.readthedocs.io/en/latest/getting_started.html ,
I would like to check a link to my example application that I built using python-twitter.
Please free to comment or link it as an example ! Thanks again :)