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
In fact, this is the only service for which I had to add an environment variable to allow quickly disabling tests without a commit: a6af73a. And I occasionally have to switch on that env to make the test suite pass.
The current issue is that along with "connection refused" errors the service returns an inadequate address value: #437
I believe that level of service is inappropriate for a public API, so I'm considering removing GeocodeFarm geocoder in geopy 2.2, to avoid anyone wasting their time on a service which is that unstable.
The text was updated successfully, but these errors were encountered:
May I suggest adding it back, as it is now extremely stable and reliable. It was a downtime issue back then, but was resolved after the time it was removed from here. There are people still asking to use your solution, but cannot as it isn't in the newer packages, forcing them to use other soultions.
GeocodeFarm is the only geocoder which tests constantly fail due to the service availability issues. I have observed:
In fact, this is the only service for which I had to add an environment variable to allow quickly disabling tests without a commit: a6af73a. And I occasionally have to switch on that env to make the test suite pass.
The current issue is that along with "connection refused" errors the service returns an inadequate address value: #437
I believe that level of service is inappropriate for a public API, so I'm considering removing GeocodeFarm geocoder in geopy 2.2, to avoid anyone wasting their time on a service which is that unstable.
The text was updated successfully, but these errors were encountered: