Hey Community 
,
On Community Cloud we’ve been testing using uv instead of pip for dependencies during app wake up and when deploying an app. It’s been really promising and we’re seeing notable improvements. We’re getting ready to release this update to the community and the process is pretty straightforward.
What does this mean for you?
You don’t have to do anything–we’ll default to uv instead of pip when waking up apps or deploying apps, and if for some reason uv doesn’t work for your apps, they should automatically default to pip. The only notable impact to your accounts should be improved wake up and deployment times. 
What if you want to keep the old way?
As a workaround, you can migrate your requirements.txt (pip) to Pipfile (pipenv) if you’d like your apps to not use uv:
- Install Pipenv (pip install pipenv);
- Run pipenv install on the same folder that you have your requirements.txt file;
- Delete your requirements.txt file, as now you have Pipfile and Pipfile.lock files.
Hope everyone’s week has been going well and feel free to reach out with any questions or if you run into any problems. 