Skip to content

Latest commit

 

History

History
154 lines (102 loc) · 4.58 KB

CHANGELOG.md

File metadata and controls

154 lines (102 loc) · 4.58 KB

IPInfo Changelog

5.4.1

  • Fix bug causing batch requests to fail when using prefixed data

5.4.0

  • Add support for IPinfo Residential Proxy Detection API

5.3.0

  • Add support for IPinfo Core API
  • Add support for IPinfo Plus API

5.2.1

  • Fix Lite API Detail object not setting certain fields correctly

5.2.0

  • Add support for IPinfo Lite API

5.1.1

  • No-op release (testing Github Publishing)

5.1.0

  • Fix getDetails JSON error on 5xx status code

5.0.1

  • Fixed a bug where in the sync handler's batch functions and in the async handler's batch iterator function, the same IP was getting added twice to the lookup list if it wasn't in the cache.

5.0.0

  • BREAKING: No longer requiring a JSON file for changing the country/currency/etc data that's returned. Will now accept an in-memory map.
  • Throwing general API error responses as proper APIError error types.
  • Added an iterator version of getting batch IPs. See getBatchDetailsIter in the handler.

4.4.3

  • Added CountryFlagURL to the details object.
  • Allowed custom headers

4.4.2

  • Patch fix for empty ip_address crash.

4.4.1

  • Patch fix for handler crashing in windows environment.
  • Added bogon check locally.

4.4.0

  • Added CountryFlag to the details object.
  • Added CountryCurrency to the details object.
  • Added Continent to the details object.
  • Handled timeour error properly.

4.3.1

  • Patch fix to include eu.json in manifest for release.

4.3.0

  • Added isEU to the details object to check whether the IP geolocates to a European Union (EU) country.

4.2.1

  • Allow deleting from the cache via the del keyword, e.g. del handler.cache[ip_key].

4.2.0

  • Cache keys are now versioned. This allows more reliable changes to cached data in the future without causing confusing incompatibilities. This should be transparent to the user. This is primarily useful for users with persistent cache implementations.
  • Add Map integration. See https://ipinfo.io/map for details.

4.1.0

  • The SDK version is available via ipinfo.version as SDK_VERSION.
  • Most private functions on all handlers (i.e. those that start with _) are now moved to ipinfo.handler_utils.
  • All constants that existed on handlers (i.e. REQUEST_TIMEOUT_DEFAULT) are now moved to ipinfo.handler_utils.
  • Cache behavior for the synchronous handler is a bit different now; the item actually cached is the item after formatting is complete, rather than before.
  • Both the sync and async handlers have the following improvements:
    • timeout can be specified as a keyword-arg to getDetails to optionally override the client-level timeout.
    • getBatchDetails now has no limit to the size of the ip_addresses input list. It will chunk the list internally and make requests against the batch endpoint in a way that doesn't exceed the API's own limits.
    • getBatchDetails now accepts the new options batch_size, timeout_per_batch, timeout_total and raise_on_fail. Please see the documentation for details on what each of these do.

4.0.0

Breaking Changes

  • PR #32 All EOL Python versions are no longer supported; currently, Python 3.6 or greater is now required. An asynchronous handler is available from getHandlerAsync which returns an AsyncHandler which uses aiohttp.

3.0.0

Breaking Changes

  • PR #19 DefaultCache requires keyword arguments now instead of positional arguments, in particular maxsize and ttl.

Bug Fix

  • PR #19 Issue #18 An issue with the handler not being created if you provide your own custom maxsize/ttl values has been fixed.

2.1.0

General

  • Released a batch ops function on the handler called getBatchDetails which accepts a list of IP addresses (or an IP address plus a path to more specific details, e.g. 8.8.8.8/country). See documentation on batch operations in the README for more details.

2.0.0

Breaking Changes

  • Fix Issue #8. Deleted the ip_address key in the details object which was of type IPv4Address.

    This allows serializing the details object (into JSON or something else) without errors by default.

    Users who expected that object type can simply pull the ip key instead and turn it into an IPv4Address object on their own.