This release is a pre-release and may not be stable for production use.
PyAnsys metapackage
Welcome to the PyAnsys metapackage repository. The pyansys metapackage provides a single package of collected PyAnsys packages that ensures compatibility of these packages amongst themselves and the Ansys product release that they are linked to.
The pyansys metapackage ensures compatibility between these PyAnsys packages:
PyACP: Pythonic interface to Ansys Composite PrepPost (ACP).
PyAdditive: Pythonic interface to the Ansys Additive service.
PyAEDT: Pythonic interface to Ansys Electronics Desktop (AEDT).
PyAnsys Geometry: Pythonic interface to the Ansys Geometry service.
PyAnsys Math: Pythonic interface to PyAnsys Math libraries.
PyAnsys Sound: Pythonic interface to Ansys Sound.
PyCFX: Pythonic interface to Ansys CFX.
PyResultExplorer: Python client library for Ansys Result Explorer to explore and visualize structural simulation results.
PyChemkin: Pythonic APIs to the Ansys Chemkin utilities and reactor models.
PyConceptEV: Pythonic interface to Ansys ConceptEV library.
PyDPF - Core: Pythonic interface to the Data Processing Framework (DPF) for building advanced and customized workflows.
PyDPF - Post: Pythonic interface to access and post process Ansys solver result files.
PyDPF - Composites: Pythonic interface to postprocess layered and short-fiber composite models.
PyDYNA: Pythonic interface to build the Ansys DYNA input deck, submit it to the Ansys LS-DYNA solver, and postprocess its results.
PyDynamicReporting: Pythonic interface to Ansys Dynamic Reporting for service and control of its database and reports.
PyEDB: Pythonic interface to the Ansys Electronics Database (EDB) client library.
PyEDB - Core: Pythonic interface to Ansys Electronics Database (EDB).
PyEnSight: Pythonic interface to EnSight, the Ansys simulation postprocessor.
PyFluent: Pythonic interface to Ansys Fluent.
PyFluent - Visualization: Pythonic interface to visualize Ansys Fluent simulations.
PyGranta: Pythonic interface to Ansys Granta MI services.
PyHPS: A Python client for Ansys HPC Platform Services (HPS).
PyLumerical: Pythonic interface to Ansys Lumerical.
PyMAPDL: Pythonic interface to Ansys MAPDL (Mechanical APDL).
PyMAPDL Reader: Pythonic interface to read legacy MAPDL result files (MAPDL 14.5 and later).
PyMechanical: Pythonic interface to Ansys Mechanical.
PyModelCenter: Pythonic interface for Ansys ModelCenter
PyMotorCAD: Pythonic interface to Ansys Motor-CAD.
PyOptislang: Pythonic interface to Ansys optislang.
PyPIM: Pythonic interface to communicate with the Ansys PIM (Product Instance Management) API.
PyPrimeMesh: Python library to acquire geometries and prepare surface and volume meshes for multiple solvers.
PyRocky: Python library to communicate with Ansys Rocky using Rocky PrePost API.
PyScadeOne: Pythonic interface for Ansys Scade One.
PySherlock: Pythonic interface to communicate with Ansys Sherlock.
PySimAI: Pythonic interface to use SimAI.
PySpeos: Python library that gathers functionalities and tools based on Speos software remote API.
PySAM SysML2: Python interface for working with SysML v2 models.
PySystemCoupling: Pythonic interface to communicate with Ansys System Coupling.
PyTurboGrid: Pythonic interface to Ansys TurboGrid, a high-quality turbomachinery meshing software app.
PyTwin: Pythonic interface to communicate with consumption workflows for Ansys digital twins.
PyWorkbench: Pythonic interface to Ansys Workbench.
Shared Components: Shared Ansys software components to enable package interoperability and minimize maintenance.
Other tools delivered as part of the metapackage are:
Ansys FileTransfer Tool: Simple gRPC API tool for moving files between a client and a remote server.
Ansys Tools Common: A collection of tools for the PyAnsys ecosystem. It provides shared utilities for discovering local Ansys product installations, launching products, managing version compatibility, and reporting Python environment package versions and system information.
Ansys Tools Protobuf Compilation Helper: Utility library to compile .proto files to Python source when building the package wheel.
Ansys Tools Visualization Interface: Python interface between PyAnsys libraries and plotting backends
PyAnsys Tools Variable Interop: Tool for defining basic variables, types, metadata, and values intended to provide interoperability between all products.
PyAnsys Units: Pythonic interface for units, unit systems, and unit conversions.
PyMaterials Manager: Python package for unifying material management across the Ansys portfolio.
Currently, the pyansys metapackage is also delivering PyAnsys-based MCP (Model Context Protocol) packages, which are:
PyMAPDL MCP: MCP server that provides seamless integration between AI assistants and Ansys MAPDL through PyMAPDL.
PyLumerical MCP: MCP server that provides seamless integration between AI assistants and Ansys Lumerical through PyLumerical.
PyFluent MCP: MCP server that provides seamless integration between AI assistants and Ansys Fluent through PyFluent.
PyMechanical MCP: MCP server that provides seamless integration between AI assistants and Ansys Mechanical through PyMechanical.
PyAEDT MCP: MCP server that provides seamless integration between AI assistants and Ansys Electronic Desktop through PyAEDT.
PyCFX MCP: MCP server that provides seamless integration between AI assistants and Ansys CFX through PyCFX.
Much effort is underway to continue expanding and developing packages in the PyAnsys GitHub account. On the Issues page for each package, you can post issues and request new features. You can also feel free to post a question on the Ansys Developer Forums.
By default, the PyAnsys metapackage installs these core modules:
Additionally, the pyansys metapackage contains certain extra targets that can be installed upon request:
mapdl-all: This target installs the core packages and PyMAPDL Reader.
fluent-all: This target installs the core packages, and PyFluent - Visualization.
tools: This target installs the core packages, Ansys FileTransfer Tool, Ansys Tools Common, PyAnsys Tools Variable Interop, PyAnsys Units, and PyMaterials Manager.
mcp: This target installs the core packages, as well as the MCP-related solutions.
all: This target installs all extra pyansys packages.
Package installation
Two installation modes are provided: user and offline.
User mode installation
Before installing the pyansys metapackage in user mode, ensure that you have the latest version of pip with this command:
python -m pip install -U pipThen, install the pyansys metapackage with this command:
python -m pip install pyansysIf you are interested in installing an extra target such as fluent-all, you use a command like this:
python -m pip install pyansys[fluent-all]If you are interested in installing a specific version such as 2023.1.0, you use a command like this:
python -m pip install pyansys==2023.1.0Offline mode installation
If you lack an internet connection on your installation machine, the recommended way of installing the pyansys metapackage is downloading the wheelhouse archive from the Releases Page for your corresponding machine architecture.
Each wheelhouse archive contains all the Python wheels necessary to install the pyansys metapackage from scratch on Windows, Linux, and MacOS from Python 3.12 to 3.14. You can install this on an isolated system with a fresh Python installation or on a virtual environment.
For example, on Linux with Python 3.12, unzip the wheelhouse archive and install it with the following commands:
unzip pyansys-v2027.1.0b3-wheelhouse-Linux-3.12-core.zip wheelhouse
pip install pyansys -f wheelhouse --no-index --upgrade --ignore-installedIf you’re on Windows with Python 3.12, unzip to a wheelhouse directory and then install using the same pip command as in the previous example.
Consider installing using a virtual environment.
Versioning system
The pyansys metapackage follows a semantic-like versioning system, though it has been adapted to the Ansys product release mechanism. Thus, this kind of versioning system is followed:
XXXX.Y.ZZWhere:
XXXX is the Ansys product release year (for example, 2022).
Y is the Ansys product release within the same year (for example, 1, which relates to R1).
ZZ is a patched version to the pyansys metapackage, if any.
Consequently, the first pyansys metapackage compatible with the 2024 R2 release would be:
2024.2.0Any subsequent patched version of this package would be:
2024.2.1
2024.2.2
2024.2.3
...You can request a specific version install when using pip to install your package:
python -m pip install pyansys==2024.2.0License and acknowledgments
All PyAnsys libraries are licensed under the MIT license.
PyAnsys libraries make no commercial claim over Ansys whatsoever. These libraries extend the functionality of Ansys products by adding Python interfaces to legally obtained software products without changing the core behaviors or licenses of the original software.
For more information on Ansys products, visit the Ansys web site.
1 maintainer
Metadata
1 maintainer
Release files for pyansys 2027.1.0b3
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 |
|---|---|---|---|---|
| pyansys-2027.1.0b3.tar.gz | 8.9 MB | With provenance | Details for pyansys-2027.1.0b3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyansys-2027.1.0b3-py3-none-any.whl | Python 3 | none | any | Details for pyansys-2027.1.0b3-py3-none-any.whl |
Total release size: 8.9 MB
Release files / pyansys-2027.1.0b3.tar.gz
| Download URL | pyansys-2027.1.0b3.tar.gz |
|---|---|
| Size | 8.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cae925a8ca7a566b8569947b2a738727f4661f2432b5c246cebe04d9f7b48483
|
|
BLAKE2b-256 checksum How to use checksums |
129172ce25d89379eef0f5f7349af2376c6afe85b2de9f6734139cddca93f5dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / pyansys-2027.1.0b3-py3-none-any.whl
| Download URL | pyansys-2027.1.0b3-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c67f58963dfe19a283d2da1366d1aa03c150693c69301d80579c2b1109392bfb
|
|
BLAKE2b-256 checksum How to use checksums |
b891dc5be13b579b4e76142c8a11ef1c60fca70539b29fba79a1ebeddfd53701
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logSecurity for pyansys 2027.1.0b3
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 pyansys-2027.1.0b3.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 Oct 28, 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.
