Rate limits remaining of Twitter API v2

Hi, using Twitter API v2, I found that we couldn’t confirm remaining of rate limits by each response with tweepy/client.py.

Rate limits doc: https://developer.twitter.com/en/docs/twitter-api/rate-limits

So, I’d like to propose to extend tweepy/client.py a little below.

# before
Response = namedtuple("Response", ("data", "includes", "errors", "meta"))

# after
Response = namedtuple("Response", ("data", "includes", "headers", "errors", "meta"))

And just add the headers of requests.response into Response in Client._make_request method.

Then, we can check the remaining of rate limits for each endpoint’s return value, such as response.headers['x-rate-limit-remaining']. I’d be grateful if you could look into that 😄

[rnakashiro]

Thank you for reply.

The use cases are, to show rate-limits for users, to prevent 429 response before API call when remaining are 0, and so on.

Official Twitter API provides a way to check rate-limits for every response, but that’s omitted now, so this lib is ideal to inherit the Twitter’s feature 😄

[rnakashiro]

Oh, sorry. I’m using with commit-hash git+https://github.com/tweepy/tweepy.git@9a28e0eaa7329918bfbf19e08afccb473210a2d1 in requirements.txt, and reviewed this lib’s code on Github.

I’m interested in Twitter API v2’s arrival and this lib’s support. So, I proposed a little change. 😄