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
First many thanks for this great work, we using it as part of our make setup for Ansible since almost 2 years already.
Today I tested to make it compatible to work with uv. In a first iteration I did quite simple changes: still using python -m venv to create the venv, but then just installing uv with pip in it. And for installing the dependencies I then use uv pip install ... instead of pip install.
Only with this the performance increase is massive, for an example repository the time for make venv changed from 2 mins to 12 seconds (!!!) with warm cache.
And the cool thing is that it's completely transparent for the user, he does not need to have uv installed or other requirements.
Thus imo it could be just enabled out of the box.
This leads to my question: Are you interested in uv support and if yes how? Enabling it per default or having an option like USING_UV for it?
I can then work on a PR for it.
Furthermore we could also detect if uv is already present and if yes use it for the venv creation, this would decrease the timing, but not that significant anymore.
The text was updated successfully, but these errors were encountered:
Hi,
First many thanks for this great work, we using it as part of our make setup for Ansible since almost 2 years already.
Today I tested to make it compatible to work with uv. In a first iteration I did quite simple changes: still using
python -m venv
to create the venv, but then just installinguv
with pip in it. And for installing the dependencies I then useuv pip install ...
instead ofpip install
.Only with this the performance increase is massive, for an example repository the time for
make venv
changed from 2 mins to 12 seconds (!!!) with warm cache.And the cool thing is that it's completely transparent for the user, he does not need to have uv installed or other requirements.
Thus imo it could be just enabled out of the box.
This leads to my question: Are you interested in uv support and if yes how? Enabling it per default or having an option like
USING_UV
for it?I can then work on a PR for it.
Furthermore we could also detect if uv is already present and if yes use it for the venv creation, this would decrease the timing, but not that significant anymore.
The text was updated successfully, but these errors were encountered: