Hi Theo,

----- Mail original -----
> As someone who usually only needs to deal with the python ecosystem
> when there's already enough other pain involved and thus has absolutely no
> patience for its idiosyncrasies, I'd very much appreciate an
> up-to-date port over having to remember how to fiddle with pip* and venvs.
> (I needed to look at some trailofbits stuff that relied heavily on
> ruff and uv, and it took ages before I could get started).

I agree. uv (and also ruff) project from Astral-sh is now very used and a great improvement for Python's ecosystem: manage deps for projects, publish it, run scripts, create and remove virtual envs...

> So the attached port does some polishing like fixing missing deps and
> wantlib and installing the shell completions.

Thanks for the merge of my port in OpenBSD-WIP and yours (with the initial work from denis@).

> It should be pretty much equivalent to Laurent's port in openbsd-wip
> except that I didn't pull in the retry counting patches since it
> wasn't clear that that was about.

No need of my patches for this. It's a workaround for the patched version of reqwest-middleware crate by Astral-sh.

> There's also the question if it should go into devel or sysutils. I
> have no real opinion on that.

I prefer 'devel' for category instead of 'sysutils' like devel/py-poetry-core, devel/py-pdm-backend... (and other Python backends/tools to manage projects).

> Someone needs to review this properly before it can go in. Once
> that's done and if Laurent or Denis are willing to take maintainer and want
> to keep this reasonably up-to-date, I think I'll be ok with someone else
> importing it.

I'm currently reviewing and building/testing your port (with some minor modifications). I would like to take maintainership for it.
I am going to send a reviewed version for devel/uv port.

PS: I will also "polish" my port for Ruff with your tricks to use patched crates. And submit it after build/tests.

Laurent