Fix finding packages witch hatchling >= 1.19.0 #137
Merged
Conversation
This file contains 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
Explicitly specify the package name to install, in order to fix compatibility with `hatchling >= 1.19.0`. Starting with this version (though Frozen-Flask is affected since 1.20.0, due to a bug in hatchling), it is necessary to explicitly select packages if they do not As of hatchling >= 1.19.0, it is necessary to explicitly specify `packages` to use if they do not fit the default heuristics (i.e. are disjoint from the project name). Since the package is now specified explicitly, the `exclude` rules are no longer necessary.
|
Thank you! |
|
Thanks! |
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.
Explicitly specify the package name to install, in order to fix compatibility with
hatchling >= 1.19.0. Starting with this version (though Frozen-Flask is affected since 1.20.0, due to a bug in hatchling), it is necessary to explicitly select packages if they do notAs of hatchling >= 1.19.0, it is necessary to explicitly specify
packagesto use if they do not fit the default heuristics (i.e. are disjoint from the project name).Since the package is now specified explicitly, the
excluderules are no longer necessary.