mirror of https://github.com/astral-sh/uv
d1f4f8a358
With the previous order of operations, there could be warnings from race conditions between two process A and B removing and installing Python versions. * A removes the files for CPython3.9.18 * B sees the key CPython3.9.18 * B sees that CPython3.9.18 has no files * A removes the key for CPython3.9.18 * B try to removes the key for CPython3.9.18, gets and error that it's already gone, issues a warning We make the more resilient in two ways: * We remove the registry key first, avoiding dangling registry keys in the removal process * We ignore not found errors in registry removal operations: If we try to remove something that's already gone, that's fine. Fixes #14714 (hopefully) |
||
|---|---|---|
| .. | ||
| sysconfig | ||
| cpuinfo.rs | ||
| discovery.rs | ||
| downloads.rs | ||
| environment.rs | ||
| implementation.rs | ||
| installation.rs | ||
| interpreter.rs | ||
| lib.rs | ||
| libc.rs | ||
| macos_dylib.rs | ||
| managed.rs | ||
| microsoft_store.rs | ||
| platform.rs | ||
| pointer_size.rs | ||
| prefix.rs | ||
| python_version.rs | ||
| target.rs | ||
| version_files.rs | ||
| virtualenv.rs | ||
| windows_registry.rs | ||