Per issue #80, this handles the new NOT_FOUND error status code returned by the Google Places API (details) so that it's handled semantically the same as the ZERO_RESULTS error status code. It also changes the in list to a tuple to improve performance.
I am dropping this issue because handling NOT_FOUND actually requires much more extensive changes to the way the library works. Better to let it keep raising an error (more specific as per issue #81).
Per issue #80, this handles the new
NOT_FOUND
error status code returned by the Google Places API (details) so that it's handled semantically the same as theZERO_RESULTS
error status code. It also changes thein
list to a tuple to improve performance.