1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
# Use uv (Experimental)
+++ 2.19.0
PDM has experimental support for [uv](https://github.com/astral-sh/uv) as the resolver and installer. To enable it:
```
pdm config use_uv true
```
PDM will automatically detect the `uv` binary on your system. You need to install `uv` first. See [uv's installation guide](https://docs.astral.sh/uv/getting-started/installation/) for more details.
## Reuse the Python installations of uv
uv also supports installing Python interpreters. To avoid overhead, you can configure PDM to reuse the Python installations of uv by:
```
pdm config python.install_root $(uv python dir)
```
## Limitations
Despite the significant performance improvements brought by uv, it is important to note the following limitations:
- The cache files are stored in uv's own cache directory, and you have to use `uv` command to manage them.
- PEP 582 local packages layout is not supported.
- `inherit_metadata` lock strategy is not supported by uv. This will be ignored when writing to the lock file.
- Update strategies other than `all` and `reuse` are not supported.
- Editable requirement must be a local path. Requirements like `-e git+<git_url>` are not supported.
- `excludes` settings under `[tool.pdm.resolution]` are not supported.
- Cross-platform lock targets are not supported by uv resolver, i.e., you can lock for platforms that are different from the current.
|
