Overview
The ansys-bdm-shared-volume package provides a concrete implementation of the Blob Data Management (BDM) interface defined by ansys-bdm-api. It uses a networked shared file-system volume as the underlying storage backend.
Within the SAF ecosystem, this package enables GLOW-based solutions to manage files and directories through the standard BDM abstractions while storing data on a shared volume that is accessible across processes and machines. This makes it well suited for desktop deployments and on-premises environments where a common network drive or local shared folder is available.
Key capabilities include:
Implementation of StorageScope and AsyncStorageScope for synchronous and asynchronous file operations.
Automatic tracking and cleanup of cached entities when a storage scope exits.
Factory utilities for creating storage scopes from configuration.
By plugging into the BDM layer, the shared-volume backend allows solution code to remain storage-agnostic: the same workflow logic can run against this backend during local development and against other BDM backends in cloud or distributed deployments.
Troubleshooting
For troubleshooting or reporting issues, please open an issue in the project repository.
Please follow these steps to report an issue:
Go to the project repository.
Click on the Issues tab.
Click on the New Issue button.
Provide a clear and detailed description of the issue you are facing.
Include any relevant error messages, code snippets, or screenshots.
Additionally, you can refer to the official documentation for additional resources and troubleshooting guides.
License
You can find the full text of the license in the LICENSE file.
Changelog
The changelog section provides a summary of notable changes for each version of BDM Shared Volume for Python. It helps you keep track of updates, bug fixes, new features, and improvements made to the project over time.
To view the complete changelog, visit the project repository and navigate to the CHANGELOG file. It provides a comprehensive list of changes categorized by version, along with brief descriptions of each change.
1 maintainer
Metadata
1 maintainer
Release files for ansys-bdm-shared-volume 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ansys_bdm_shared_volume-0.4.0.tar.gz | 17.1 kB | With provenance | Details for ansys_bdm_shared_volume-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ansys_bdm_shared_volume-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for ansys_bdm_shared_volume-0.4.0-py3-none-any.whl |
Total release size: 40.3 kB
Release files / ansys_bdm_shared_volume-0.4.0.tar.gz
| Download URL | ansys_bdm_shared_volume-0.4.0.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f3250635fb3d949ccccb8e3691ab9e94aeeba0a5f3cc663bfe3bb76f51f5d68
|
|
BLAKE2b-256 checksum How to use checksums |
c7461a5c982233a8a3679429e8b32837ae205b370f115661e1a2844bdbd73bb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 3, 2026.
Transparency logRelease files / ansys_bdm_shared_volume-0.4.0-py3-none-any.whl
| Download URL | ansys_bdm_shared_volume-0.4.0-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e02c2e300379eb8b4d56bc147b1c9f0b70747413fec867d49ea4c2d634fb3132
|
|
BLAKE2b-256 checksum How to use checksums |
e75ed3e690f42670fea42e8e5a27ff8242e6393c3ec332fde8ad9619a860c638
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 3, 2026.
Transparency logSecurity for ansys-bdm-shared-volume 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ansys_bdm_shared_volume-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
