Uv migration and explicit LICENSE #11
Merged
Conversation
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
Member
Author
|
Hi @jkim810 would be good to have your eyes over this maintenance PR when you can |
Member
|
Thank you so much for taking the time to updating the build to uv @afrendeiro ! |
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.
This is a maintenance PR which simplifies build/installation by migrating to
uvand using a modern butpip-compatiblepyproject.tomlexclusively (nosetup.pyorsetup.cfg).A LICENSE file was added keeping the previous GPLv3+ license which was only mentioned in the package metadata and wasn't parsed by Github.
Some types were simplified and updated.
Dependency versions were updated and pinned if necessary.