Use hatchling to build distribution #1112
Merged
+351
−143
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.
I've extracted just the packaging bits out of #1082 and updated them here.
Issue(s) Resolved
Fixes #1081
Related Issues / Links
Supercedes #1082
Description of Changes
Changes include:
setup.cfg
topyproject.toml
(PEP 621)publish
CI job from thepublish.yml
workflow into ourci.yml
workflow.Hatchling's support of build hooks allows us to integrate the building of our front-end JS and CSS into the PEP 517 build process. Among other things, this makes it possible to install a working version of Lektor directly from git. E.g.
will work (assuming the user has a working installation of Node/npm).
Moving the
publish
job to the main CI workflow allows for two improvements: