You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if the Google Places API returns a status other than OK or ZERO_RESULTS, the library raises a GooglePlacesError. However, that error simply has the offending status code in the exception message, which makes it hard for consuming code to figure out what happened. status_code should be an attribute of GooglePlacesError.
The text was updated successfully, but these errors were encountered:
beamerblvd
added a commit
to beamerblvd/python-google-places
that referenced
this issue
Oct 21, 2016
Per issue slimkrazy#81, added a new `GooglePlacesAPIError` to allow including `url` and `status_code` attributes that can be used by client code for better error handling. Went the route of a new, extending exception to avoid any issues with extra-party uses of the existing `GooglePlacesError`.
Currently, if the Google Places API returns a status other than
OK
orZERO_RESULTS
, the library raises aGooglePlacesError
. However, that error simply has the offending status code in the exception message, which makes it hard for consuming code to figure out what happened.status_code
should be an attribute ofGooglePlacesError
.The text was updated successfully, but these errors were encountered: