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 am stuck on the philosophical questions of: would we need to rebrand to uvenv? maybe it should be a whole new project -- but is it realistically much faster when most things are network activity of getting the wheels, and then they still need to be installed? In all seriousness though, it might be worth me taking a deeper look, but we have to admit that pipenv is a big bear hug around pip and so there is a lot to detangle there if there were a motivation to wrap a different package library.
There is a lot of discussion about the Rust-based
pip
-replacement nameduv
.Would it be of interest to accelerate
pipenv
build times by usinguv
instead ofpip
?Is your feature request related to a problem? Please describe.
I'm always frustrated when pipenv builds take several minutes.
Describe the solution you'd like
pipenv builds take seconds instead of minutes.
Describe alternatives you've considered
Switch to non-pipenv solutions for our builds.
The text was updated successfully, but these errors were encountered: