Sandu
Sandu
> with #3943 in place and people starting to have e.g. git dependencies into a package in a workspace, i'm afraid this change would cause some breakage. I believe this...
The use-case is supported using ```toml [tool.uv.sources] shared_lib = { path = "../shared_lib", editable = true} ```
> How does this differ from excluding the projects from the workspace? Excluded projects cannot use workspace dependencies, these can. And they're allowed to have conflicting dependencies because they use...
> needs some thought / discussion before committing to it. Yesterday I couldn't resist trying to implement it, it turned out to be a lot more straightforward than I expected....
> It's an interesting idea... I understand the motivation but needs some thought / discussion before committing to it. Rye had a [similar issue](https://github.com/astral-sh/rye/issues/615) raised a little while ago.
I'm getting this error consistently when I run on a Mac, but not on Linux. Dagger 0.14.0. Running: dagger shell -q s1.dag s1.dag: ``` #!/usr/bin/env dagger shell -q ctr1=$(.container |...
I noticed a significant hit if the module in part of a big repository. The initializer prints something like ``` upload [GIT_ROOT] from ... (client id: ..., session id: ...)...
I've started [experimenting](11547) with this. Have yet to do an end-to-end test.
on the `--env-file` option, it would be nice if the file content was read by the cli and then sent to the engine. That would allow [process substitution](https://en.wikipedia.org/wiki/Process_substitution) to work.