tools/mpremote: Automate building mpremote distribution wheel. #8404
Conversation
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
6f97663 to
cc10aba
Compare
Codecov Report
@@ Coverage Diff @@
## master #8404 +/- ##
==========================================
- Coverage 98.40% 98.26% -0.14%
==========================================
Files 153 154 +1
Lines 20189 20292 +103
==========================================
+ Hits 19866 19939 +73
- Misses 323 353 +30
Continue to review full report at Codecov.
|
dpgeorge
pushed a commit
to jimmo/micropython
that referenced
this pull request
Feb 24, 2023
This allows the entire configuration to be defined in a single file, including the logic for including pyboard.py and automatically versioning based on the git tag. Building the package works both via `python -m build` as well as `hatch build`. `python -m build ` has the advantage of automatically fetching all dependencies, you don't need to manually install any hatch packages. In order to make the versioning work, and also keep things simpler for end users, mpremote releases will now be the same as MicroPython releases and use the same tag. The version strings for mpremote will look like: - X.Y.Z -- clean build at the tag - X.Y.Z.postN+gHASH -- clean build, N revisions from the most recent tag - X.Y.Z.postN+gHASH.dYYYYMMDD -- dirty build, N revisions from out This commit extends on the idea from micropython#8404. Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
|
Closed in favour of #10645. |
karfas
pushed a commit
to karfas/micropython
that referenced
this pull request
Apr 23, 2023
This allows the entire configuration to be defined in a single file, including the logic for including pyboard.py and automatically versioning based on the git tag. Building the package works both via `python -m build` as well as `hatch build`. `python -m build ` has the advantage of automatically fetching all dependencies, you don't need to manually install any hatch packages. In order to make the versioning work, and also keep things simpler for end users, mpremote releases will now be the same as MicroPython releases and use the same tag. The version strings for mpremote will look like: - X.Y.Z -- clean build at the tag - X.Y.Z.postN+gHASH -- clean build, N revisions from the most recent tag - X.Y.Z.postN+gHASH.dYYYYMMDD -- dirty build, N revisions from out This commit extends on the idea from micropython#8404. Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
alphonse82
pushed a commit
to alphonse82/micropython-wch-ch32v307
that referenced
this pull request
May 8, 2023
This allows the entire configuration to be defined in a single file, including the logic for including pyboard.py and automatically versioning based on the git tag. Building the package works both via `python -m build` as well as `hatch build`. `python -m build ` has the advantage of automatically fetching all dependencies, you don't need to manually install any hatch packages. In order to make the versioning work, and also keep things simpler for end users, mpremote releases will now be the same as MicroPython releases and use the same tag. The version strings for mpremote will look like: - X.Y.Z -- clean build at the tag - X.Y.Z.postN+gHASH -- clean build, N revisions from the most recent tag - X.Y.Z.postN+gHASH.dYYYYMMDD -- dirty build, N revisions from out This commit extends on the idea from micropython#8404. Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
tannewt
added a commit
to tannewt/circuitpython
that referenced
this pull request
Sep 22, 2023
Update bpi_leaf_s3
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.
As part of my additions to mpremote in #8231 I found it difficult to package up an installation wheel of mpremote to test and share with others.
This PR uses what I believe it the new best practices in python packaging to hook the build system to do things like copy extra files into the package distribution (eg.
pyboard.py) and build said wheel with Github Actions.I've also added a development marker to the version number for master builds showing the number of commits since release, eg
mpremote-0.2.0+1-py3-none-any.whlOn the git commit where the version number is set this marker will not be present.