This is a module reimplemented specifically for MicroPython standard library, with efficient and lean design in mind. Note that this module is likely work in progress and likely supports just a subset of CPython’s corresponding module. Please help with the development if you are interested in this module.
1 maintainer
Metadata
1 maintainer
Release files for micropython-opcode 0.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 | Actions |
|---|---|---|---|---|
| micropython-opcode-0.0.tar.gz | 530 Bytes | Without provenance | Details for micropython-opcode-0.0.tar.gz |
Release files / micropython-opcode-0.0.tar.gz
| Download URL | micropython-opcode-0.0.tar.gz |
|---|---|
| Size | 530 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59c0762cb226037cfe2ffb84fe97373f512542de3c6499ae1463ff396db69a3e
|
|
BLAKE2b-256 checksum How to use checksums |
8639d4fd914878e5ed6af37f879e506f323fd8d66cd86d7777609ce163d3d539
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Security for micropython-opcode 0.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.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
