Since pyperformance users include not only CPython but also alternative implementations, I don’t think relying on uv would be a good approach for us to take. cc@hugovk

uv supportsCPython, PyPy, GraalPy and Pyodidie

--python accepts binaries, eg custom PyPy3 build:

10:36:09.653252000AM CET maurycy@gimel /Users/maurycy/src/pyperformance % uv run --isolated --project=benchmarks/bm_sympy --python=`which pypy3` benchmarks/bm_sympy/run_benchmark.py      Built psutil==7.1.2Installed 4 packages in 68ms.......sympy_expand: Mean +- std dev: 73.9 ms +- 6.0 ms.......sympy_integrate: Mean +- std dev: 22.5 ms +- 3.8 ms.......sympy_sum: Mean +- std dev: 46.7 ms +- 6.6 ms.......sympy_str: Mean +- std dev: 51.1 ms +- 11.6 ms

If I understand correctly,the only requirement is that-I,-B and-C needs to be supported by an interpreter. I might be totaly wrong here, though.uv seems to checksys.implementation.name andmatch it

refastral-sh/uv#2096

No there are a lot of implementations over you listed. e.g RustPython Jython gpython. Let s not make a big huddle to them.

Unless you have a strong motivation to maintain this project based on uv, let's keep it as is based on standard(pip).
I love uv but this should consider other factors.

No there are a lot of implementations over you listed. e.g RustPython Jython gpython. Let s not make a big huddle to them.

That doesn't matter. Not to diss the other implementations, but they most likely can't even run pip. If you can't even run pip, there's no point supporting these.

1. RustPython can't run pipTracking pip support in RustPython RustPython/RustPython#5332
2. Jython only supports Python 2.7, which clearly can't use pyperformance.
3. GPython saysgpython does not include many python modules as many of the core modules are written in C not python. So that's also not gonna work.

There's a reason to not switch to uv by default though --- that would be a breaking change of pyperformance likely requiring a major version bump.

@maurycy I think this is really great work and I would be willing to accept this PR if the default stayed pip, but you allow an option/command line flag to switch to uv. Then I think@corona10's concerns should be solved.

FWIW, starting a pip subprocess is extremely slow on other implementations like GraalPy. Even on CPython it is slow. Running a benchmarking run on GraalPy might be faster if we switch to uv, so I'm very much looking forward to this change.

@maurycy I think this is really great work and I would be willing to accept this PR if the default stayed pip, but you allow an option/command line flag to switch to uv. Then I think@corona10's concerns should be solved.

It will be fine with switching to uv as an optional feature as Ken Jin commented.

RustPython can't run pipRustPython/RustPython#5332

For clarity, they can run old pip but fail with the latest pip; anyway, they have a chance to run pyperformance using old pip.
RustPython/RustPython#5332 (comment)
so switching to uv by default will be a big hurdle for new challengers :)