pyproject.toml
adapter for uv
writes to the filesystem within the project root, breaks down in read-only situations
#3292
Labels
🐛 bug
Something isn't working
Describe the bug
To support
uv
(indeed, a feature not yet production ready in the current implementation), thepyproject.toml
file gets moved away and the contents at its path mutate. Afteruv
completes,pdm
restores the originalpyproject.toml
.This doesn't work when the filesystem is read-only (in some place). This design also creates some noise in IDEs that watch the filesystem and thing the VCS working copy is undergoing changes.
I haven't studied the current implementation in detail, but creating a temporary directory and/or files using e.g., the
tempfile
module is more likely to get past this filesystem constraint.To reproduce
Expected Behavior
Don't assume renames etc. are possible and avoid filesystem mutations as much as possible.
Environment Information
pdm -v output
No response
Additional Context
When
pyproject.toml
is a read-only bind mount, it's simply impossible to rename as far as I know.Are you willing to submit a PR to fix this bug?
The text was updated successfully, but these errors were encountered: