Tim de Jager
Tim de Jager
Locking the build-backends is something that is being discussed in the pypi world as well. So that should be useful for sure, currently UV does another resolve to determine the...
`NoBuildIsolation` is possible for sure, we should give that a go!
Hmm I understand, let me think about it more, I'll come back to this.
I think, what you **actually** want might be a build and install in the current environment functionality, which would replace your use-case for editables as dependencies?
Can we close this for now with the abiliy to specify `no-build-isolation`?
Do note that as a small workaround you can use pixi tasks for this. E.g something like: ```toml #... rest of pyproject.toml [tool.pixi.feature.publish.dependencies] # For building wheel using hatch hatch...
Actually I would've expected the env variable to be set by the CUDA activation script. These should be passed to the PyPI build. @baszalmstra do you know something about the...
We do pass env variables to uv for sure, otherwise things like c compilers wouldn't work also. And I believe we use the 'activator' for that.
Yeah and try if a non-conda vim install does not do exhibit the same behavior.
@baszalmstra to clarify the first part of your statement. If you have environment `a` and `b` that are part of the solve-group `foo`. Then we solve once for `foo` and...