You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a quick search, I wasn't able to find any similar request. I haven't thought very deeply about how this would all work but at a high-level, there's often the requirement to have other tool dependencies in development (I'm considering runtime dependencies like native shared libraries separately).
I could imagine a this taking a couple different forms:
a flavor of uv tool ... that's a wrapper around some other tool runner eg npx. Some examples include the supabase cli (npx) for local development and ci/cd. I could also imagine things like the work needed for the pyright wrapper https://pypi.org/project/pyright/ wouldn't be needed for such tools.
Sometimes you just need native deps eg in the bio world, you find yourself installing things like samtools, bowtie etc because their python wrappers just expect the binary on your path. Bio-conda is one approach to solving the bio informatics toolchain setup. When I also need those on the deployment environment, I currently make sure they're installed in the deployed docker image.
There's obviously prior art in this space (coda, pixie, nix dev-envs/determinant-systems, ...).
Example
No response
The text was updated successfully, but these errors were encountered:
Summary
After a quick search, I wasn't able to find any similar request. I haven't thought very deeply about how this would all work but at a high-level, there's often the requirement to have other tool dependencies in development (I'm considering runtime dependencies like native shared libraries separately).
I could imagine a this taking a couple different forms:
uv tool ...
that's a wrapper around some other tool runner egnpx
. Some examples include the supabase cli (npx) for local development and ci/cd. I could also imagine things like the work needed for the pyright wrapper https://pypi.org/project/pyright/ wouldn't be needed for such tools.There's obviously prior art in this space (coda, pixie, nix dev-envs/determinant-systems, ...).
Example
No response
The text was updated successfully, but these errors were encountered: