Debug GraalPy/uv test failures on Windows (#2741)
* Dont attempt uv frontend tests on gp311. * docs: note GraalPy 3.11 incompatibility with uv on Windows (#2751) * Initial plan * docs: note GraalPy311 incompatibility with uv/build[uv] on Windows Co-authored-by: joerick <1244307+joerick@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: joerick <1244307+joerick@users.noreply.github.com> * Skip both graalpy with uv for now * Docs updates --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: joerick <1244307+joerick@users.noreply.github.com>
This commit is contained in:
co-authored by
joerick
copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Copilot
parent
0a85e29549
commit
b70562f37a
@@ -482,6 +482,11 @@ uv currently does not support iOS or musllinux on s390x, ppc64le and riscv64.
|
||||
You can also use the `uv` backend directly; though currently multiple output
|
||||
files (from workspaces) are not supported.
|
||||
|
||||
!!! note
|
||||
There is currently a compatibility issue between GraalPy and uv. If you
|
||||
are building GraalPy wheels, use `build` or `pip` as the build frontend
|
||||
instead of `build[uv]` or `uv`.
|
||||
|
||||
On Android and Pyodide, the "pip" frontend is not supported.
|
||||
|
||||
You can specify extra arguments to pass to the build frontend using the
|
||||
|
||||
Reference in New Issue
Block a user