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
I'm wondering if anyone has come across the uv package handler. In addition to package dependency resolution speed, it is also optimized for quick iteration of python environments, so that they can be built, re-built, cached (so they're only re-built when required), etc, as well as for running single file scripts, much like the contents of the benchmarks directory. It seems like asv and uv might be a great fit.
Is there any interest in expanding asv to allow for a uv environment type?
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up! I think it'd be a good idea, but perhaps it would work better as a plugin? I'm looking to reduce the functionality of the main repository; though I haven't yet thought too much about the design of the "resolvers", and we have (IMO) too many already, virtualenv (now the default, and dependencies come with asv) along with mamba (which has its own dependencies) and conda (which is basically driven by subprocess.
Thanks for the awesome package!
I'm wondering if anyone has come across the
uv
package handler. In addition to package dependency resolution speed, it is also optimized for quick iteration of python environments, so that they can be built, re-built, cached (so they're only re-built when required), etc, as well as for running single file scripts, much like the contents of thebenchmarks
directory. It seems likeasv
anduv
might be a great fit.Is there any interest in expanding
asv
to allow for auv
environment type?The text was updated successfully, but these errors were encountered: