Lors de l'utilisation de tweepy curseur, Quelle est la meilleure pratique pour détecter les erreurs de capacité?
je rassemble des informations sur un grand nombre d'utilisateurs utilisant la bibliothèque Twepy de Python. J'ai initialisé L'API comme suit
api = tweepy.API (auth, wait_on_rate_limit=True, wait_on_rate_limit_notify=True)
où auth contient mes jetons. Ce code répond bien aux erreurs de limite de taux, mais ne fonctionne pas pour d'autres erreurs. Par exemple, je vois parfois, l'exception suivante.
tweepy.error.TweepError: [{'message': 'Over capacity', 'code': 130}]
je peux gérer cette exception en utilisant un try except, mais je me demandais s'il y avait un moyen de gérer cette exception dans le curseur comme je gère les exceptions de limite de vitesse. Je vois des paramètres comme retry_count, mais je ne suis pas sûr qu'ils fonctionneront dans ce cas car ils semblent conçus pour les erreurs HTTP.
12
demandé sur
user1507889
2018-01-05 19:01:38
1 réponses
je vois des paramètres comme retry_count, mais je ne suis pas sûr qu'ils fonctionneront pour ce cas comme ils semblent conçus pour les erreurs HTTP.
Eh bien, selon le docs, certains paramètres ont un correspondant de code HTTP, qui indique qu'il fonctionnera. (Liste complète ci-dessous ma réponse)
sur toute la liste, vous êtes intéressé par
Plus de capacité correspond à HTTP 503. Twitter est temporairement dépassé par la capacité
Donc, ce que vous avez besoin est de fournir un retry_errors param lors de l'instanciation du API. Cela indiquera à l'API les codes de statut HTTP à réessayer. Un exemple:
retry_count=10, retry_delay=5, retry_errors=set([503])
liste complète des codes:
+------+--------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Code | Text | Description |
+------+--------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 3 | Invalid coordinates | Corresponds with HTTP 400. The coordinates provided as parameters were not valid for the request. |
| 13 | No location associated with the specified IP address | Corresponds with HTTP 404. It was not possible to derive a location for the IP address provided as a parameter on the geo search request. |
| 17 | No user matches for specified terms | Corresponds with HTTP 404. It was not possible to find a user profile matching the parameters specified. |
| 32 | Could not authenticate you | Corresponds with HTTP 401. There was an issue with the authentication data for the request. |
| 34 | Sorry, that page does not exist | Corresponds with HTTP 404. The specified resource was not found. |
| 36 | You cannot report yourself for spam. | Corresponds with HTTP 403. You cannot use your own user ID in a report spam call. |
| 44 | attachment_url parameter is invalid | Corresponds with HTTP 400. The URL value provided is not a URL that can be attached to this Tweet. |
| 50 | User not found. | Corresponds with HTTP 404. The user is not found. |
| 63 | User has been suspended. | Corresponds with HTTP 403 The user account has been suspended and information cannot be retrieved. |
| 64 | Your account is suspended and is not permitted to access this feature | Corresponds with HTTP 403. The access token being used belongs to a suspended user. |
| 68 | The Twitter REST API v1 is no longer active. Please migrate to API v1.1. | Corresponds to a HTTP request to a retired v1-era URL. |
| 87 | Client is not permitted to perform this action. | Corresponds with HTTP 403. The endpoint called is not a permitted URL. |
| 93 | This application is not allowed to access or delete your direct messages | Corresponds with HTTP 403. The OAuth token does not provide access to Direct Messages. |
| 99 | Unable to verify your credentials. | Corresponds with HTTP 403. The OAuth credentials cannot be validated. Check that the token is still valid. |
| 120 | Account update failed: value is too long (maximum is nn characters) | Corresponds with HTTP 403. Thrown when one of the values passed to the update_profile.json endpoint exceeds the maximum value currently permitted for that field. The error message will specify the allowable maximum number of nn characters. |
| 130 | Over capacity | Corresponds with HTTP 503. Twitter is temporarily over capacity. |
| 131 | Internal error | Corresponds with HTTP 500. An unknown internal error occurred. |
| 135 | Could not authenticate you | Corresponds with HTTP 401. Timestamp out of bounds (often caused by a clock drift when authenticating - check your system clock) |
| 144 | No status found with that ID. | Corresponds with HTTP 404. The requested Tweet ID is not found (if it existed, it was probably deleted) |
| 150 | You cannot send messages to users who are not following you. | Corresponds with HTTP 403. Sending a Direct Message failed. |
| 151 | There was an error sending your message: reason | Corresponds with HTTP 403. Sending a Direct Message failed. The reason value will provide more information. |
| 160 | You've already requested to follow user | Corresponds with HTTP 403. This was a duplicated follow request and a previous request was not yet acknowleged. |
| 161 | You are unable to follow more people at this time | Corresponds with HTTP 403. Thrown when a user cannot follow another user due to some kind of limit |
| 179 | Sorry, you are not authorized to see this status | Corresponds with HTTP 403. Thrown when a Tweet cannot be viewed by the authenticating user, usually due to the Tweet’s author having protected their Tweets. |
| 185 | User is over daily status update limit | Corresponds with HTTP 403. Thrown when a Tweet cannot be posted due to the user having no allowance remaining to post. Despite the text in the error message indicating that this error is only thrown when a daily limit is reached, this error will be thrown whenever a posting limitation has been reached. Posting allowances have roaming windows of time of unspecified duration. |
| 186 | Tweet needs to be a bit shorter. | Corresponds with HTTP 403. The status text is too long. |
| 205 | You are over the limit for spam reports. | Corresponds with HTTP 403. The account limit for reporting spam has been reached. Try again later. |
| 215 | Bad authentication data | Corresponds with HTTP 400. The method requires authentication but it was not presented or was wholly invalid. |
| 220 | Your credentials do not allow access to this resource. | Corresponds with HTTP 403. The authentication token in use is restricted and cannot access the requested resource. |
| 251 | This endpoint has been retired and should not be used. | Corresponds to a HTTP request to a retired URL. |
| 261 | Application cannot perform write actions. | Corresponds with HTTP 403. Thrown when the application is restricted from POST, PUT, or DELETE actions. Check the information on your application dashboard. See How to appeal application suspension and other disciplinary actions. |
| 271 | You can’t mute yourself. | Corresponds with HTTP 403. The authenticated user account cannot mute itself. |
| 272 | You are not muting the specified user. | Corresponds with HTTP 403. The authenticated user account is not muting the account a call is attempting to unmute. |
| 323 | Animated GIFs are not allowed when uploading multiple images. | Corresponds with HTTP 400. Only one animated GIF is allowed to be attached to a single Tweet. |
| 324 | The validation of media ids failed. | Corresponds with HTTP 400. There was a problem with the media ID submitted with the Tweet. |
| 325 | A media id was not found. | Corresponds with HTTP 400. The media ID attached to the Tweet was not found. |
| 326 | To protect our users from spam and other malicious activity, this account is temporarily locked. | Corresponds with HTTP 403. The user should log in to https://twitter.com to unlock their account before the user token can be used. |
| 327 | You have already retweeted this Tweet | Corresponds with HTTP 403. The user cannot retweet the same Tweet more than once. |
| 354 | The text of your direct message is over the max character limit. | Corresponds with HTTP 403. The message size exceeds the number of characters permitted in a Direct Message. |
| 385 | You attempted to reply to a Tweet that is deleted or not visible to you. | Corresponds with HTTP 403. A reply can only be sent with reference to an existing public Tweet. |
| 386 | The Tweet exceeds the number of allowed attachment types. | Corresponds with HTTP 403. A Tweet is limited to a single attachment resource (media, Quote Tweet, etc.) |
+------+--------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
5
répondu
Adelin
2018-01-10 11:09:02