Switch from rye to uv for package management #128
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
Another run at #123 with thanks to @hugovk for the initial PR and the push to get to grips with this. This commit is pretty much the same as was done in that PR, and carries over a lot of code. However I initially had to back it out because it killed my ability to publish Hike. Now I've done a much of reading I think I'm confident that it can be used without too much effort. That is, I think I've managed to gain the minimum amount of trust I need in it to be able to make the switch. It's... not as good as rye, as I'm seeing it so far, but advantages exist and I can work around the friction that uv introduces. Of course the main motivation is that the bait and switch of rye->uv has finally happened. It's yet another reason for folk to view Python packaging tools with deep (and justified) suspicion.
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.
Another run at #123 with thanks to @hugovk for the initial PR and the push to get to grips with this. This supersedes #127 too (which got into a bit of a mess and at this point I'm better off starting fresh).
This commit is pretty much the same as was done in that PR, and carries over a lot of code. However I initially had to back it out because it killed my ability to publish Hike.
Now I've done a much of reading I think I'm confident that it can be used without too much effort. That is, I think I've managed to gain the minimum amount of trust I need in it to be able to make the switch.
It's... not as good as rye, as I'm seeing it so far, but advantages exist and I can work around the friction that uv introduces.
Of course the main motivation is that the bait and switch of rye->uv has finally happened. It's yet another reason for folk to view Python packaging tools with deep (and justified) suspicion.