HERE SDK for Python V2
8 days ago by ReadMe API
Changes released before 2025-09-29 are on the archived changelog.
Version
Change
Description
2.35.0
REMOVED
KeplerGL package is not maintained anymore and not release for newer versions
of Python. Therefore the support for KeplerGL by Python SDK was removed.
of Python. Therefore the support for KeplerGL by Python SDK was removed.
2.35.0
ADDED
Added RETRY_MAX_WAIT config option, defaulting to 60, which sets the
maximum value for exponential retries. Avoids long retry max times (e.g. 10
or 20 minutes) having retry intervals that are potentially several minutes
apart, which can make it less likely that a request will go through if the
service is still flaky.
maximum value for exponential retries. Avoids long retry max times (e.g. 10
or 20 minutes) having retry intervals that are potentially several minutes
apart, which can make it less likely that a request will go through if the
service is still flaky.
2.34.0
ADDED
Added a check of authorization errors for the error code used by the AAA API for a
duplicate nonce. This causes a NonceAlreadyUsedException, which can be
captured for a retry.
duplicate nonce. This causes a NonceAlreadyUsedException, which can be
captured for a retry.
2.34.0
CHANGED
While the x-idempotency-key header is explicitly documented for managing
subscriptions to identify retry requests, other APIs may use it as well
despite not being documented. The most notable example is the blob API,
where a put request uses the idempotency key and content length to identify
a retry, while other standard retries (e.g. in response to a 429 error) may
result in a 409 conflict if the backend still managed to process the
request before the error response was sent.
Removed the explicit idempotency key management for subscriptions in favor
of the shared behavior. Also removed some documentation for creating an
idempotency key where it was completly unused.
subscriptions to identify retry requests, other APIs may use it as well
despite not being documented. The most notable example is the blob API,
where a put request uses the idempotency key and content length to identify
a retry, while other standard retries (e.g. in response to a 429 error) may
result in a 409 conflict if the backend still managed to process the
request before the error response was sent.
Removed the explicit idempotency key management for subscriptions in favor
of the shared behavior. Also removed some documentation for creating an
idempotency key where it was completly unused.
2.34.0
CHANGED
Send X-HERE-Digest header for blob v1 and v2 puts to validate integrity of
data that is uploaded. A digest mismatch is checked within "400" responses to
retry if the data wasn't properly sent.
data that is uploaded. A digest mismatch is checked within "400" responses to
retry if the data wasn't properly sent.
2.34.0
CHANGED
Due to HMC schema change the deprecated curvature_heading attribute was
replaced by dedicated curvature and heading attributes in here-content/HMC2.
replaced by dedicated curvature and heading attributes in here-content/HMC2.
2.33.0
FIXED
Fixed an issue where multi-part uploads using aiohttp ignored environment proxy settings.
2.33.0
FIXED
Added retry handling for ChunkedEncodingError in standard (non-streaming) requests, preventing immediate failures and improving resilience to transient network issues.
2.33.0
FIXED
Added retry logic for multi-part partition blob uploads in the Python SDK, preventing failures on transient errors (e.g., HTTP 429) and improving reliability.
2.32.0
ADDED
Added support for http streaming with retries and respecting "next"
field for the response when listing partitions or changes
from the Metadata API. This will catch errors when iterating over the
chunks and retry with a Range header to start where it left off. This
improves both the existing use case of downloading blobs with streaming
mode, which bypasses the typical retry behavior for the initial request,
as well as for streaming extremely large partition lists that can extend
for many minutes or even hours.
field for the response when listing partitions or changes
from the Metadata API. This will catch errors when iterating over the
chunks and retry with a Range header to start where it left off. This
improves both the existing use case of downloading blobs with streaming
mode, which bypasses the typical retry behavior for the initial request,
as well as for streaming extremely large partition lists that can extend
for many minutes or even hours.
2.32.0
ADDED
Added support for python 3.13 and 3.14 in the SDK packages.
2.32.0
CHANGED
Added support for HMC v2.3 which adds support for topology-attributes layer
and removes support for all other *-attributes layers.
and removes support for all other *-attributes layers.
2.32.0
DEPRECATED
Deprecation notice for support of keplergl in here-inspector. It will be removed in June 2026 release.