From 135fae7bfe12e98a1d2004e8f10522058968a49a Mon Sep 17 00:00:00 2001 From: Zanie Blue Date: Mon, 9 Dec 2024 09:22:29 -0600 Subject: [PATCH] Fix build failure links --- docs/reference/build_failures.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/build_failures.md b/docs/reference/build_failures.md index d9a792284087..b010e3142eeb 100644 --- a/docs/reference/build_failures.md +++ b/docs/reference/build_failures.md @@ -78,7 +78,7 @@ ModuleNotFoundError: No module named 'distutils' !!! important The `--use-pep517` flag should be included with the `pip install` invocation to ensure the same - build isolation behavior. uv always uses [build isolation by default](https://docs.astral.sh/uv/pip/compatibility.md#pep-517-build-isolation). + build isolation behavior. uv always uses [build isolation by default](../pip/compatibility.md#pep-517-build-isolation). We also recommend including the `--force-reinstall` and `--no-cache` options when reproducing failures. @@ -304,6 +304,6 @@ numpy<1.23; python_version < "3.10" ### Package is only usable on a specific platform If locking fails due to building a package that is only usable on another platform, you can -[provide dependency metadata manually](https://docs.astral.sh/uv/reference/settings.md#dependency-metadata) -to skip the build. uv can not verify this information, so it is important to specify correct -metadata when using this override. +[provide dependency metadata manually](./settings.md#dependency-metadata) to skip the build. uv can +not verify this information, so it is important to specify correct metadata when using this +override.