David Poznik

Hi, I'm working with a long-ago forked version, and I'm getting exactly this warning. I'm curious if the issue was ever resolved? If not, any suggestions? I imagine it arises...

I've run into this issue as well and figured I'd post my example in case helpful: ``` $ cat foo.py from metaflow import batch # type: ignore from metaflow import...

Yes, BT is about as broad as it gets (see page 5 of the [manuscript](https://www.biorxiv.org/content/10.1101/088716v1)) and unlikely to be the right call. If you run with the `--all_aux_output` option, Yhaplo...

> Any suggestions on how to make this clearer? Perhaps something like the following, wherein instances of "package" have been edited to forms of "dependency" to disambiguate "packages" providing tools...

Relatedly, does `uv tool` have an equivalent to `pipx`'s [`reinstall-all`](https://pipx.pypa.io/stable/docs/#pipx-reinstall-all) subcommand? I find this useful when, for example, upgrading Python.

> You can do `uv tool upgrade --all`. You can even do `uv tool upgrade --all --python 3.13` to upgrade all installed tools to Python 3.13. Ah, so `uv tool...

> As a heads up I'll be looking into some other inconsistencies of `@resources` as well next week that have been on the backlog for a while now, and will...

> As a heads up I'll be looking into some other inconsistencies of `@resources` as well next week that have been on the backlog for a while now, and will...

> For the time being, I would say lets keep the PR open as still relevant. Cool, will do. Thanks for the update!