PyMaterials Manager is a Python package for unifying material management across the Ansys portfolio.
PyMaterials Manager is currently a proof of concept, expect things to break. It currently provides the following features:
It defines a Material Object that can have different material models
The supported material models can be read from a running PyMAPDL instance
The supported material models can written to a running PyMAPDL / pyFluent instance
Some supported material models can be read from a MatML XML file
Some supported material models can be written to a MatML XML file
The following material models are supported:
- pyMAPDL
Simple constant material properties
Piecewise linear material properties
Polynomial material properties
Anisotropic Elasticity
- pyFluent
Simple constant material properties
Ideal Gas properties
Installation
Install the ansys-materials-manager package with this code:
pip install ansys-materials-managerAlternatively, clone and install this package with this code:
git clone https://github.com/ansys/pymaterials-manager
cd pymaterials-manager
pip install .Testing
This project takes advantage of tox. This tool is used to automate common development tasks (similar to Makefile), but it is oriented towards Python development.
Use tox
tox uses environments, which are similar to Makefile rules, to make it highly customizable. In fact, this tool creates its own virtual environment so that anything being tested is isolated from the project to guarantee the project’s integrity.
Descriptions follow of some of the most widely used environments:
tox -e style: Checks the code style of your project.
tox -e py: Runs your test suite.
tox -e doc: Builds the documentation of your project.
Perform raw testing
If required, you can call style commands (such as black, isort, and flake8) or unit testing commands (such as pytest) from the command line. However, calling these commands does not guarantee that your project is being tested in an isolated environment, which is the reason why tools like tox exist.
Use pre-commit
The style checks take advantage of pre-commit. Developers are not forced but encouraged to install this tool by running this command:
python -m pip install pre-commit && pre-commit installEvery time you stage some changes and try to commit them, pre-commit only allows them to be committed if all defined hooks succeed.
Documentation and issues
For comprehensive information on PyMaterials Manager, see the latest release documentation. On the PyMaterials Manager Issues page, you can create issues to submit questions, report bugs, and request new features. This is the best place to post questions and code.
Distribution
If you want to create either source or wheel files, start by installing poetry and then executing the build module. To install poetry you should use the pipx installation method in the poetry documentation.
poetry install
poetry build
twine check ./dist1 maintainer
Metadata
1 maintainer
Release files for ansys-materials-manager 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 | |
|---|---|---|---|---|
| ansys_materials_manager-0.4.0.tar.gz | 43.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_materials_manager-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 158.6 kB
Release files / ansys_materials_manager-0.4.0.tar.gz
| Download URL | ansys_materials_manager-0.4.0.tar.gz |
|---|---|
| Size | 43.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be5c850faa5ea02e9708891eaa6c621960bd1da87280c4d7592ed9b127b86cc8
|
|
BLAKE2b-256 checksum How to use checksums |
77d7094222753864151aaf24872a089e4954bd4e01ee0c3a69827186d32078a7
|
| 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 May 29, 2026.
Transparency logRelease files / ansys_materials_manager-0.4.0-py3-none-any.whl
| Download URL | ansys_materials_manager-0.4.0-py3-none-any.whl |
|---|---|
| Size | 115.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98d699dabbfa48b9661dc7c4f275d3269517ff594836aa9f8cbb9d2d4ea90df2
|
|
BLAKE2b-256 checksum How to use checksums |
25fa20b88e520b5597d28635a42c8c9ec8a43634c02263b31d1647f0f86ff664
|
| 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 May 29, 2026.
Transparency logSecurity for ansys-materials-manager 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_materials_manager-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 May 29, 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.
