senml: Allow publishing to PyPI as micropython-senml. #636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a mechansim to allow micropython-lib packages to be published to PyPI for use by CPython.
The idea is that there are some packages (in the micropython directory) that do not have CPython counterparts -- essentially our version is the "original" or "upstream" for these packages. As opposed to a package in the python-stdlib or python-ecosys directories, where the micropython-lib is our version of those packages -- if you were using CPython you'd use the "real" one instead.
This adds a tool that can parse a package's manifest and generate a Python project directory (with pyproject.toml) suitable for building and uploading to PyPI. (Note this requires micropython/micropython#11162 to be merged first).
This is enabled for the micropython/senml package which has no counterpart in the PyPI. Note that this depends on cbor2, which does exist in PyPI, so the CPython version, micropython-senml will depend on the "real" version instead.