Version 3.9.0
This release focuses mostly on the changes regarding the Sentinel Hub configuration file (SHConfig
) moving into the direction of a more common config usage:
- The format of the config file has been changed from JSON to TOML, which offers a more intuitive overview
- The config parameters can now be provided as input in the class constructor
- The location of the config file has been changed to
~/.config/sentinelhub/config.toml
on Linux/MacOS andC:/Users/<USERNAME>/.config/sentinelhub/config.toml
on Windows, which means that the configs are now separated from the repo location- all environments where
sentinelhub-py
is installed now use the configuration from the same source - installing new versions now doesn't reset the configuration
- all environments where
- The option of having multiple configuration files was removed
- Profiles were introduced, allowing users to define and use multiple profiles defined in the same location
- only the updated fields are present in the configuration, the rest are equal to the default configuration parameters
- A limited support of environment variables was introduced.
SH_PROFILE
that dictates which profile should be used when not explicitly provided.SH_CLIENT_ID
andSH_CLIENT_SECRET
for setting the SentinelHub credentials.
- The general precedence order of the provided parameters is
explicit parameters > environment > configuration file > defaults
.
For more information about the configuration updates, check the Configuration section in the readthedocs.
Other changes in this release include:
- Removed support for Python 3.7. This should help with an easier Conda installation
- The package is now released as a wheel
- Added support for Async Process API
- Switched to a
pyproject.toml
based install, enabling a lighter package with fewer install files - Increased tests performance and cleaned up deprecated functions