Descarteslabs

Latest version: v3.1.0

Safety actively analyzes 628936 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 18

2.0.0rc5

Catalog

- Loosen up the restrictions on the allowed alphabet for Blob names. Now almost any printable
character is accepted save for newlines and commas.
- Added new storage types for Blobs: `StorageType.COMPUTE` (for Compute job results) and
`StorageType.DYNCOMP` (for saved `dynamic-compute` operations).

Compute

- Added testing of the client.

2.0.0rc4

Catalog

- The defaulting of the `namespace` value for `Blob`s has changed slightly. If no namespace is specified,
it will default to `<org>:<hash>` with the user's org name and unique user hash. Otherwise, any other value,
as before, will be prefixed with the user's org name if it isn't already so.
- `Blob.get` no longer requires a full id. Alternatively, you can give it a `name` and optionally a `namespace`
and a `storage_type`, and it will retrieve the `Blob`.
- Fixed a bug causing summaries of `Blob` searches to fail.

Compute

- `Function.map` and `Function.rerun` now save the created `Job`s before returning.
- `Job.get` return values fixed, and removed an extraneous debug print.

General

- Updated requirements to avoid `urllib3>=2.0.0` which break all kinds of things.

2.0.0rc3

Geo

- The defaulting of `align_pixels` has changed slightly for the `AOI` class. Previously it always defaulted to
`True`. Now the default is `True` if `resolution` is set, `False` otherwise. This ensures that when specifying
a `shape` and a `bounds` rather than a resolution,the `shape` is actually honored.
- When assigning a `resolution` to an `AOI`, any existing `shape` attribute is automatically unset, since the
two attributes are mutually exclusive.
- The validation of bounds for a geographic CRS has been slightly modified to account for some of the irregularities
of whole-globe image products, correcting unintended failures in the past.

Catalog

- The default `geocontext` for image objects no longer specifies a `resolution` but rather a `shape`, to ensure
that default rastering preserves the original data and alignment (i.e. no warping of the source image).
- The `Blob.upload` and `Blob.upload_data` methods now return `self`, so they can be used in a fluent style.
- As with `resolution`, you can now pass a `crs` parameter to the rastering methods (e.g. `Image.ndarray`,
`ImageCollection.stack`, etc.) to override the `crs` of the default geocontext.

Compute

- A bevy of fixes to the client.

2.0.0rc2

Catalog

- Added support for data storage. The `Blob` class provides mechanism to upload, index, share, and retrieve arbitrary byte sequences (e.g. files). `Blob`s can be searched by namespace and name, geospatial coordinates (points, polygons, etc.), and tags. `Blob`s can be downloaded to a local file, or retrieved directly as a Python `bytes` object. `Blob`s support the same sharing mechanisms as `Product`s, with `owners`, `writers`, and `readers` attributes.
- Added support to `Property` for `prefix` filtering.

Compute

- Added method to update user credentials for a `Function`.
- Added methods to retrieve build and job logs.

General

- Added support for Shapely=2.X.

2.0.0rc1

- This is an internal-only release. There is as of yet no updated documentation. However, the user-facing client APIs remain fully compatible with v1.12.1.

Compute

- Added support for managed batch compute under the `compute` module.

Auth and Configuration

- Removed the check on the Auth for configuration, since it is all AWS all the time.

Raster Client

- Fixed a bug in the handling of small blocks (less than 512 x 512) that caused rasterio to generate bad download files (the desired image block would appear as a smaller sub-block rather than filling the resulting raster).

2.0.0rc0

- This is an internal-only release. There is as of yet no updated documentation. However, the user-facing client APIs remain fully compatible with v1.12.1.

Supported platforms

- Deprecated support for Python 3.7 (will end of life in July).
- Added support for Python 3.10 and Python 3.11
- AWS-only client. For the time being, the AWS client can be used to communicate with the legacy GCP platform (e.g. `DESCARTESLABS_ENV=gcp-production`) but only supports those services that are supported on AWS (`catalog` and `scenes`). This support may break at any point in the future, so it is strictly transitional.

Dependencies

- Removed many dependencies no longer required due to the removal of GCP-only features.

Configuration

- Major overhaul of the internals of the config process. To prepare for supporting other clients using namespaced packages within the `descarteslabs` package, the top level has been cleaned up, and most all the real code is down inside `descarteslabs.core`. However end users should never have to import anything from `descarteslabs.core`. No more magic packages means that `pylint` will work well with code using `descarteslabs`.
- GCP environments only support `catalog` and `scenes`. All other GCP-only features have been removed.

Catalog

- A bug in the code handling the default context for image collections when working with a product with a CRS based on degrees rather than meters has been fixed. Resolutions should always be specified in the units used by the CRS.

Page 4 of 18

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.