PyEDB-Core is a Python client for the Electronics Database (EDB), a format for storing information describing designs for Ansys Electronic Desktop (AEDT). Using the PyEDB-Core API, you can make calls to an EDB server that is running either locally or remotely.
The EDB server can create, edit, read, and write EDB files to disk. These files can then be read into AEDT and their designs simulated.
Documentation and issues
Documentation for the latest stable release of PyEDB-Core is hosted at PyEDB-Core documentation. The documentation has five sections:
Getting started: Describes how to install PyEDB-Core in user mode.
User guide: Describes how to use PyEDB-Core.
API reference: Provides API member descriptions and usage examples.
Examples: Provides examples showing end-to-end workflows for using PyEDB-Core.
Contribute: Describes how to install PyEDB-Core in developer mode and how to contribute to this PyAnsys library.
In the upper right corner of the documentation’s title bar, there is an option for switching from viewing the documentation for the latest stable release to viewing the documentation for the development version or previously released versions.
On the PyEDB-Core Issues page, you can create issues to report bugs and request new features. When possible, use these issue templates:
Bug report template
Feature request template
Documentation issue template
Example request template
If your issue does not fit into one of these categories, create your own issue.
On the Discussions page on the Ansys Developer portal, you can post questions, share ideas, and get community feedback.
To reach the PyAnsys support team, email pyansys.core@ansys.com.
License
PyEDB-Core is licensed under the MIT license.
PyEDB-Core makes no commercial claim over Ansys whatsoever. The use of this Python client requires a legally licensed copy of AEDT. For more information, see the Ansys Electronics page on the Ansys website.
1 maintainer
Metadata
1 maintainer
Release files for ansys-edb-core 0.3.3
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_edb_core-0.3.3.tar.gz | 174.9 kB | With provenance | Details for ansys_edb_core-0.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ansys_edb_core-0.3.3-py3-none-any.whl | Python 3 | none | any | Details for ansys_edb_core-0.3.3-py3-none-any.whl |
Total release size: 416.9 kB
Release files / ansys_edb_core-0.3.3.tar.gz
| Download URL | ansys_edb_core-0.3.3.tar.gz |
|---|---|
| Size | 174.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad7eab6b2134b78370a71f2c9a17a9faae562a6e0e8bb6279c8a93523fec04a6
|
|
BLAKE2b-256 checksum How to use checksums |
f035512d053e53bb11af8c1e3741c60e03c88288c7e45bd75fa44ff89ca5ed8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jun 24, 2026.
Transparency logRelease files / ansys_edb_core-0.3.3-py3-none-any.whl
| Download URL | ansys_edb_core-0.3.3-py3-none-any.whl |
|---|---|
| Size | 242.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
992602e86ec6528d0514614cb5411b4d48496285eee80127959a7f84a0d2fa5b
|
|
BLAKE2b-256 checksum How to use checksums |
a45be3be9731ae0a973956091e65570783236268e2f8b0f1eb71725001129a32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jun 24, 2026.
Transparency logSecurity for ansys-edb-core 0.3.3
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_edb_core-0.3.3.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 Jun 24, 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.
