Changelog
This changelog is generated automatically from GitHub Releases.
freezebase 0.5.0
2026-08-24 · GitHub
Added
- Python 3.14 support
freezebase.__version__, read from the installed distribution metadata.
Fixed
- HTTPDownloader now closes the streamed response on every path out of a download, not only on the successful one.
freezebase 0.4.0
2026-08-17 · GitHub
Added
- HTTPDownloader.close() and context-manager support, which close the downloader’s session and release its pooled connections. Creating one downloader per download previously held a connection open until the garbage collector ran, which made downstream test suites fail unpredictably. The session is also closed on garbage collection as a fallback.
Changed
- Breaking: HTTPDownloader no longer forwards arbitrary keyword arguments to
requests.methodandtimeoutare now named parameters and are spelled exactly as before, so calls that only used those keep working;methodis restricted to"GET"and"POST". Any otherrequestskeyword, such asparamsorheaders, now raisesTypeErrorinstead of reaching the request. To configure the transport, for example a connection pool size, mount an adapter onHTTPDownloader.session.
freezebase 0.3.0
2026-08-05 · GitHub
This release marks the first release of freezebase on PyPI!
Added
- Per-path named AWS profile support in make_s3_upath. Combinable with a custom
endpoint_url, mutually exclusive withanon=Trueand explicitkey/secret/token. Setting a profile takes environment credentials out of boto’s resolution chain, so the path signs with the profile’s keys only. aws_session, returning the cached RasterioAWSSessionfor an S3 path, andclear_aws_session_cacheto discard those sessions. Preferaws_sessionover constructing anAWSSessiondirectly, so every layer signs identically.
Changed
- Renamed the package to
freezebase, to allow publication on PyPI under the same name. The import path, PyPI distribution name,FREEZEBASE_CACHE/FREEZEBASE_DATAenvironment variables, and the GitHub repository all changed accordingly; there is no compatibility shim for the old names. - s3_env reuses a cached
AWSSessionper distinct S3 configuration instead of building one per call. Constructing a session resolves boto’s whole credential chain eagerly, and s3_env is entered on every raster operation, so a profile-authenticated path previously re-read the shared credentials file for every raster read and write. Refreshable STS/SSO credentials still rotate, because Rasterio re-freezes them on eachEnventry; static credentials rewritten mid-process now needclear_aws_session_cache. - make_s3_upath rejects credentials in
client_kwargs, which reach s3fs but not s3_env.