Repository navigation
PyPI pointers: old pydevices-* names install their new packages - #177
Merged
Merged
Conversation
One last release of each retired name, one patch above its last version: no code, a dependency on the new name and a README that says where it went, so an old install line still works. The workflow builds them from scripts/build_pypi_pointers.py and uploads by Trusted Publishing from the pypi-pointers environment, which allows main only. Built all nine locally: twine check --strict passes on 18 files, each wheel holds only metadata, and installing the palettes and mpftp pointers pulled in omnipython-palettes and a working mcuctl.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Nine package names were retired when the packages moved to their omnipython-* names and mcuctl. This adds one last release for each of them, one patch above its last version: no code, a dependency on the new name, and a README saying where the package went and what to import. An old
pip install pydevices-lvglkeeps working and brings in omnipython-lvgl.scripts/build_pypi_pointers.pyholds the nine names, versions and READMEs.publish-pypi-pointers.ymlis dispatched by hand from main: it builds them, runstwine check --strict, and uploads by Trusted Publishing from thepypi-pointersenvironment, which allows the main branch only.I built all nine locally: twine check passes on all 18 files, each wheel holds only its metadata, and installing the palettes and mpftp pointers into a fresh venv pulled in omnipython-palettes (imports) and mcuctl (runs). The unit test fails when a pointer's dependency loses its new name. The upload itself is not run here; it needs each name's Trusted Publisher registered first.