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
Why these changes are being introduced:
uv is a modern python project and dependency manager with increasingly
attractive features and community support. By contrast, pipenv is
feeling a bit stale in terms of features, community support, and
even performance.
Additionally, without going into great detail here, uv is part of
a larger ecocsystem of python tooling that work very well together,
including uv, ruff, and ty (type checking).
How this addresses that need:
* Virtually anywhere pipenv was used, uv is now used
* Makefile updated to use uv
* Makefile installation recipes updated to utilize uv best
* Dockerfile updated to align with uv installation approaches
Side effects of this change:
* Before this template code can be used by a project,
Github actions will need to be updated to intelligently
use pipenv or uv depending on the project as we incrementally
convert them.
Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/IN-1298
0 commit comments