Solution Application Framework - SAF Desktop Installer
Overview
The SAF Desktop Installer enables packaging SAF-based solutions into standalone, distributable installers for desktop deployment. It is part of the Solution Application Framework (SAF) toolchain and is typically invoked through the saf build command provided by the SAF CLI.
The generated installer is self-contained: it bundles the solution code, all Python dependencies, and the Python interpreter itself, so end users can run the solution without needing a pre-configured development environment. Ansys products and other external tools required by the solution must still be installed separately on the target machine.
Key capabilities include:
Standalone packaging: Uses PyInstaller to produce a single installer that includes all necessary dependencies and a Python interpreter.
Cross-platform support: Generates installers compatible with the operating system where the build is executed (Windows .exe or Linux executable).
Online and offline modes: By default, installers download dependencies at install time; the --offline-package option bundles everything for environments without internet access.
Customizable build options: Supports encryption, code obfuscation, custom entry points, and configurable Python versions.
Documentation embedding: Automatically builds and embeds Sphinx documentation so users can access it offline from within the solution.
From a workflow perspective, SAF Desktop Installer is the final step in preparing a solution for distribution. Once a solution has been developed and tested locally using SAF CLI and SAF Desktop Orchestrator, the installer packages it into a form that can be delivered to end users or deployed across an organization.
Installation
Ensure you have all the necessary prerequisites. Then, refer to the installation guidelines for detailed instructions on how to install the project in your system.
Documentation
The official documentation of SAF Desktop Installer contains the following chapters:
Getting started. This section provides a brief overview and instructions on how to get started with the project. It typically includes information on how to install the project, set up any necessary dependencies, and run a basic example or test to ensure everything is functioning correctly.
User guide. The user guide section offers detailed documentation and instructions on how to use the project. It provides comprehensive explanations of the project’s features, functionalities, and configuration options. The user guide aims to help users understand the project’s concepts, best practices, and recommended workflows.
Contribute. This section provides guidelines and instructions on how to contribute to the project. It includes information on how to set up the development environment, run tests, submit pull requests, and follow contribution guidelines.
Troubleshooting
For troubleshooting or reporting issues, open an issue in the project repository.
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
This project is licensed under the Apache 2.0 License - see the LICENSE file for details.
Changelog
The changelog section provides a summary of notable changes for each version of SAF Desktop Installer 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.
Metadata
Release files for ansys-saf-desktop-installer 1.17.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_desktop_installer-1.17.0.tar.gz | 133.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_saf_desktop_installer-1.17.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 275.0 kB
Release files / ansys_saf_desktop_installer-1.17.0.tar.gz
| Download URL | ansys_saf_desktop_installer-1.17.0.tar.gz |
|---|---|
| Size | 133.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0aaea41e277bb82563e88fb525907c2394dec1b9058750073e044ea5cc29cea4
|
|
BLAKE2b-256 checksum How to use checksums |
a2ed51b2e88634e9cae01f2ec7fc2e7a03a9a3dd4a4febd28e117bc7cdc34026
|
| 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_desktop_installer-1.17.0-py3-none-any.whl
| Download URL | ansys_saf_desktop_installer-1.17.0-py3-none-any.whl |
|---|---|
| Size | 141.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
50598fd98b0863706925ab82218f467cf7e807a1dbdc7cce600d330a8b106ddc
|
|
BLAKE2b-256 checksum How to use checksums |
ddb12c690be472daabab100a1e7ee6d1526ec3d328ec8458da560b7db2455ac4
|
| 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