This release is a pre-release and may not be stable for production use.
freecad-typings
Type stubs for the FreeCAD Python API, version 1.0.0rc2.
Generated from FreeCAD 26.3.0.RC2. This package versions the FreeCAD Python API, not
the FreeCAD release: the major and minor components change when the API itself changes, so a
given stub version can describe more than one FreeCAD release.
This package provides PEP 561 py.typed stubs generated from FreeCAD's
C++ Python bindings, so static type checkers and IDEs can understand the
FreeCAD objects, modules, and functions available at runtime.
Installation
pip
pip install freecad-typings
uv
uv add freecad-typings
Modules
The stubs cover the public FreeCAD Python modules, including FreeCAD,
FreeCADGui, Part, and the other core workbench modules.
Usage
Once installed, type checkers (e.g. pyright, pyre, mypy) and editors
will automatically pick up the stubs for the FreeCAD modules.
These stubs are generated and intended for static analysis; they are not a runtime replacement for the real FreeCAD binary.
Release files for freecad-typings 1.0.0rc2
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 | |
|---|---|---|---|---|
| freecad_typings-1.0.0rc2.tar.gz | 171.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| freecad_typings-1.0.0rc2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 375.3 kB
Release files / freecad_typings-1.0.0rc2.tar.gz
| Download URL | freecad_typings-1.0.0rc2.tar.gz |
|---|---|
| Size | 171.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c9c3542b1e735c6e8dc80937dbc22a2d8896da3f3d48e3690a4f603b1f708385
|
|
BLAKE2b-256 checksum How to use checksums |
bf6d74d0967c3075248a3d4bd090243cc23cb36ad9f28a53117dc655c8e6ebc7
|
| 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 Oct 18, 2026.
Transparency logRelease files / freecad_typings-1.0.0rc2-py3-none-any.whl
| Download URL | freecad_typings-1.0.0rc2-py3-none-any.whl |
|---|---|
| Size | 203.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c29f60de2967c6eab2616e7a63dee3a3fdc12520c9eaafbaac66beab49a0611f
|
|
BLAKE2b-256 checksum How to use checksums |
1ac80c285a794ade6ab34e7bce021b23d7ce0ccf4edb2d976baa008765423f34
|
| 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 Oct 18, 2026.
Transparency logSecurity for freecad-typings 1.0.0rc2
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 freecad_typings-1.0.0rc2.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 18, 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.
