Open nightblure opened 2 weeks ago
The hint is here
DEBUG No static
pyproject.toml
available for: pixi @ file:///Users/ivan/Desktop/work/pixi (PyprojectToml(FieldNotFound("version")))
Since we can't find a version
field in your project, we need to ask a build backend to retrieve that metadata for us.
We should error or something here though since package = false
is set.
upd
I deleted the setup.py file and got this message in its clear form:
ValueError: invalid pyproject.toml config: `project`.
configuration error: `project` must contain ['version'] properties
Could a good way out of this be a logic where uv would not ask for the version when we get option package = false
? We may not require a version at all, or we may already manage versioning (not of a package, but of a web service in my case) using bump2version or any other utility. In PDM this is exactly how it works, because now I'm trying to switch from it to uv
Hi! I finally took the time to try using this amazing tool in one of the working services but found the following problem. When I try to create a lock file with disabled package control mode (
package = false
in tool.uv section), I get an error:I think this is due to the fact that I have a setup.py file in the current directory that may be accessing a requirements.txt file that does not exist. here is part of the code from setup.py:
And actually what prompted me to create this is that I specified in pyproject.toml the option to disable managing the project as a package, I assume that uv would not try to build the package, and therefore would not look into setup.py at all. My pyproject.toml:
uv lock --verbose
uv --version
):uv 0.4.18 (Homebrew 2024-10-01)