Conversation
Member
Author
|
This works fine but the base uv image needs to be pushed for the subsequent jobs to succeed. |
PPC64 (big endian) seems dead, and it's only supported on one exact manylinux version (pypa/auditwheel#669), so we should drop it. This change does not affect PPC64LE (little endian).
…#17660) Stabilize `uv add --bounds` and the `add-bounds` configuration option. There's not many usages of the features, but there also aren't any problem reports, and I don't expect its functionality to change unless there were bigger `uv add` and/or argument/configuration handling changes. * https://github.com/search?q=path%3A**%2F*.toml%20add-bounds&type=code * https://grep.app/search?regexp=true&q=uv+add.*--bounds * https://github.com/search?q=%22uv+add%22+%22--bounds%22&type=code&p=1 Not breaking, but queuing up for 0.10 since it fits nicely with that release.
Closes #17368 Co-authored-by: Claude <noreply@anthropic.com>
Same as #17756 for pyodide
Since you cannot reference these indexes, I don't think we need a warning and deprecation period. Co-authored-by: Claude <noreply@anthropic.com>
…all` (#14112) Closes #12921 For `uv tool run`, we'll just use the global Python version for all invocations without an explicit alternative request (i.e., via the `--python` flag). For `uv tool install`, it's a bit more complicated: - If the tool is not installed, we'll use the global Python version - If the tool is already installed, we won't change the Python version unless `--reinstall` or `--python` is used - If the tool was installed with `--python`, we won't use the global Python version, unless the tool is uninstalled first The behavior can be demonstrated as follows ``` $ uv python pin --global 3.12 $ uv tool install flask # uses 3.12 $ uv tool install flask # no-op $ uv python pin --global 3.13 $ uv tool install flask # no-op $ uv tool install flask --reinstall # uses 3.13 $ uv tool install flask -p 3.12 # uses 3.12 $ uv tool install flask # no-op $ uv tool install flask --reinstall # uses 3.12 ``` This is a little more complicated than always reinstalling when the global Python version pin changes, but I think it's probably more intuitive when actually using the tool. We briefly touched on this when adding global version pins at #12115 (comment) Minor note: I need to do a self-review of this implementation, as it's a little awkward to encode this behavior in the existing logic.
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
3 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.
Closes #17764
This is on top of #17661 because bookworm doesn't support riscv64