Migrate to flit - #971
Open
zxzxwu wants to merge 1 commit into
Open
Conversation
Collaborator
Author
|
@barbibulle Do we have any preference here? Recently I saw some discussion about deprecation of setuptools. Though there is no official announcement about that, some documents hint that setuptools is no longer the top choice, unless with any native extension. Some direct advantages I saw with flit:
But we will also need to move apps and tools to under |
Collaborator
|
I think it's a great idea to move to a newer packaging tool. I don't have any experience with flit or hatchling, but both seem like they would work nicely here. |
Collaborator
Author
|
Hatchling looks more flexible. If we want to keep the current layout, it would be the best choice. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.