micropython-stm32-stubs
This is a stub-only package for MicroPython. It is intended to be installed in a projects virtual environment to allow static type checkers and intellisense features to be used while writing Micropython code.
The version of this package is alligned the the version of the MicroPython firmware.
- Major, Minor and Patch levels are alligned to the same version as the firmware.
- The post release level is used to publish new releases of the stubs.
For Micropython 1.17 the stubs are published as 1.17.post1 ... 1.17.post2
for Micropython 1.18 the stubs are published as 1.18.post1 ... 1.18.post2
To install the latest stubs:
pip install -I micropython-<port>-stubs where port is the port of the MicroPython firmware.
To install the stubs for an older version, such as MicroPython 1.17:
pip install micropython-stm32-stubs==1.17.* which will install the last post release of the stubs for MicroPython 1.17.
As the creation of the stubs, and merging of the different types is still going though improvements, the stub packages are marked as Beta.
To upgrade stubs to the latest stubs for a specific version use pip install micropython-stm32-stubs==1.17.* --upgrade
If you have suggestions or find any issues with the stubs, please report them in the MicroPython-stubs Discussions
For an overview of Micropython Stubs please see: https://micropython-stubs.readthedocs.io/en/main/
- List of all stubs : https://micropython-stubs.readthedocs.io/en/main/firmware_grp.html
Included stubs:
- Merged stubs from
stubs/micropython-v1_19_1-stm32-merged - Frozen stubs from
stubs/micropython-v1_19_1-frozen/stm32/GENERIC - Core Stubs from
stubs/micropython-core
| origin | Family | Port | Board | Version |
|---|---|---|---|---|
| Firmware | micropython | stm32 | PYBv1.1 with STM32F405RG | v1.19.1 |
| Documentation | micropython | - | - | v1.19.1 |
| Core | micropython | stm32 | - | v1.19.1 |
1 maintainer
Metadata
1 maintainer
Release files for micropython-stm32-stubs 1.19.1.post11
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 | |
|---|---|---|---|---|
| micropython_stm32_stubs-1.19.1.post11.tar.gz | 102.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| micropython_stm32_stubs-1.19.1.post11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 224.1 kB
Release files / micropython_stm32_stubs-1.19.1.post11.tar.gz
| Download URL | micropython_stm32_stubs-1.19.1.post11.tar.gz |
|---|---|
| Size | 102.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2a9669f9b919919e304d2f8af3b6cd75b1736487c9bfbd69f111664cee1414b
|
|
BLAKE2b-256 checksum How to use checksums |
3f36b774c085672d33d4777e1909679719493f29320c30b06e7727c094772960
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.6 Windows/10
|
Release files / micropython_stm32_stubs-1.19.1.post11-py3-none-any.whl
| Download URL | micropython_stm32_stubs-1.19.1.post11-py3-none-any.whl |
|---|---|
| Size | 121.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ddcc3f077f9dfa06573ad1d360fa290d925deeabb995955734c34c1fdfd5576
|
|
BLAKE2b-256 checksum How to use checksums |
ae9cb142c654cfcbce6762b8372aad973bb89dfdf4bea3a3646bbbf6cffea02d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.6 Windows/10
|
Security for micropython-stm32-stubs 1.19.1.post11
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
