GitLab

Closes #782

Closes #698

I fixed `urllib.urlencode` to `urlencode` in line 135

Fixing the cache key for both get and store methods

This feels too deep/verbose to be logged at the `info` level.

According to https://dev.twitter.com/rest/reference/post/media/upload
the limit of this endpoint is 5MB (which is 4883KiB) per file.

Currently the stall_warnings parameter is unavailable for the sample endpoint.

Python has issues representing status IDs with integers, so this will solve an issue when replying to tweets.
More info at https://dev.twitter.com/overview/api/tweets

This also fixes https://github.com/tweepy/tweepy/issues/615 by properly
decoding the python3 bytes object to a string.

Added additional params to .friends(). Now you can request the latest status (skip_status) and that the user entity be returned with the request (include_user_entities)

See https://dev.twitter.com/rest/reference/get/account/verify_credentials

Line 286.

This prevents the "RuntimeError: No active exception to reraise" error.

http://stackoverflow.com/a/28871066

Didn't look like anyone had changed the line.

Can't believe this hasn't been in until now! Huh.

Passing the tweet text as the lone positional argument to update_status:

     api.update_status(u'Hi mum!')

is suggested in much documentation and in several tests, but f99b1da5
introduced media_ids as the first argument, breaking this API.

This change will break anyone who uses tweepy >= 3.2 and assumes they
can pass media_ids as the first positional; but I expect that to be a
much smaller set than people who have followed the example in the docs,
who find their application mysteriously fails to post tweets after
upgrading tweepy.

Fixes #554.

This resolves an issue found here: https://github.com/tweepy/tweepy/issues/570

If an exception is thrown in the listener, the exception is not sent out currently and results in an error.

Made catch statement error message more explicit for _pack_image