Bug: Rate limit manager incorrectly throws an error for HTTP status 201

[mr-devs]

Despite not being present on Twitter's list of HTTP errors, it seems like when streaming rules are created, they return the successful 201 HTTP status code (details).

If the rate_limit_manager is enabled, the manager will throw an error even though we had no problems.

We should be able to edit the below line...

osometweet/osometweet/rate_limit_manager.py

Line 94 in f512660

if response.status_code != 200:

... to match either of these codes with something like...

if response.status_code not in [200, 201]:

[mr-devs]

Note: The temporary solution for this problem is simply to authorize your bearer_token with manage_rate_limits=False.

For example, see the streaming wiki page for an example.

This works because setting it to False turns off the rate limit manager and your script does not have a chance to incorrectly throw this error.

[mr-devs]

Update: The streaming endpoints now throw an error if you try to use them without the above-mentioned solution in place.