This is a dummy implementation of a module for MicroPython standard library. It contains zero or very little functionality, and primarily intended to avoid import errors (using idea that even if an application imports a module, it may be not using it onevery code path, so may work at least partially). It is expected that more complete implementation of the module will be provided later. Please help with the development if you are interested in this module.
1 maintainer
Metadata
1 maintainer
Release files for micropython-io 0.1
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-io-0.1.tar.gz | 668 Bytes | Without provenance | Details |
Release files / micropython-io-0.1.tar.gz
| Download URL | micropython-io-0.1.tar.gz |
|---|---|
| Size | 668 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc869010deef1eea666df016b4ef2c6ac080ded8c927850b704264b944e19d50
|
|
BLAKE2b-256 checksum How to use checksums |
8588233cf6fe24296acf0eb89319a22a21c896e49b74491c514af55cee91bd54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for micropython-io 0.1
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.
