Migrate to poetry 2.0.0 #621
Draft
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
Merged
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.
What this does
Poetry 2.0.0 seems to have performance issues when solving dependencies.
Generating this new
poetry.lockfile took more than 17mn (1038.1s)Using the
--regenerateoption, this was even worse as I had to killed it after 47mn (it hadn't finished)This standardizes the
pyproject.tomlto conform exactly to PEP 621 as it's now possible to do with poetry 2.0.0 which just released.How it was tested
TODO
How to checkout & try? (for the reviewer)
TODO