Solution Application Framework - SDK
ansys-saf-sdk is a meta-package that bundles the core SAF packages into a single, versioned package. It has no code of its own — it only declares dependencies on the individual SAF packages, pinned to their latest compatible versions.
Note: Installing ansys-saf-sdk requires pip 26.0 or higher.
Core dependencies
Installing ansys-saf-sdk installs these packages by default:
ansys-bdm-apiansys-bdm-shared-volumeansys-saf-glow-engineansys-iam-oidcansys-saf-product-configurationansys-saf-product-manager
Extras
Optional extras pull in additional packages, or extras of the core packages, for specific scenarios:
| Extra | Description |
|---|---|
core-dash |
GLOW engine support for Dash-based frontends. |
core-pim |
GLOW engine support for Product Instance Management (PIM). |
core-hps |
GLOW engine support for HPC Platform Services (HPS). |
core-test |
GLOW engine testing utilities. |
core-mcp |
GLOW engine support for the Model Context Protocol (MCP). |
core-all |
All optional extras of the core packages. |
instance-management |
Product configuration and product manager packages. |
instance-management-fluent |
Instance management support for Ansys Fluent. |
instance-management-aedt |
Instance management support for Ansys Electronics Desktop (AEDT). |
instance-management-optislang |
Instance management support for optiSLang. |
instance-management-geometry |
Instance management support for Ansys Geometry. |
instance-management-mapdl |
Instance management support for Ansys MAPDL. |
instance-management-mechanical |
Instance management support for Ansys Mechanical. |
instance-management-visor |
Instance management support for Visor-based products. |
instance-management-all |
All instance management product integrations. |
desktop |
Desktop orchestrator, for running solution applications as desktop apps. |
build |
Desktop installer, for building standalone desktop installers. |
all |
Every optional extra combined. |
1 maintainer
Metadata
1 maintainer
Release files for ansys-saf-sdk 0.2.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 | |
|---|---|---|---|
| ansys_saf_sdk-0.2.0.tar.gz | 7.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_saf_sdk-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.6 kB
Release files / ansys_saf_sdk-0.2.0.tar.gz
| Download URL | ansys_saf_sdk-0.2.0.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de9146eb74e67ec74f2264870ceb6bab852246158faef21100d421a36b6b6233
|
|
BLAKE2b-256 checksum How to use checksums |
ad9f8d3af619b4da5e2cba5d13a8143bc901a5505074b39f10f22f354f238960
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency logRelease files / ansys_saf_sdk-0.2.0-py3-none-any.whl
| Download URL | ansys_saf_sdk-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e210d1ffbe570448784f37698f9a7f4643167576b8dd0b688cd7d5beb22bd09
|
|
BLAKE2b-256 checksum How to use checksums |
ca9ee7499704459c18bbe7794bc55d0d334695cc726af7433948ca34326ea0a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency log
