Load micropackage dependencies statically #2989
Closed
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.
Description
This avoids building the wheel in an isolated environment just to extract the dependencies.
Cons: It relies on a PEP-621 compliant
pyproject.toml
file to be present, which only happens for Kedro projects created after #2280 was closed. Therefore, it is backwards incompatible.Pros: It makes
kedro micropkg pull
fast again, cutting the time to run the full test suite in ~half (from 12 to 7 minutes on Linux, from 14 to 6 minutes on Windows 🎉)Development notes
This uses
pyproject-metadata
instead of PyPA/build, see https://pypi.org/project/pyproject-metadata/Checklist
RELEASE.md
file