{"repo":"osprey-oss/migrate-to-uv","free":true,"listed":false,"github":"https://github.com/osprey-oss/migrate-to-uv","clone":"git clone https://github.com/osprey-oss/migrate-to-uv.git","description":"Migrate a project from Poetry/Pipenv/pip-tools/pip to uv package manager","language":"Rust","stars":1157,"topics":["pip","pip-tools","pipenv","poetry","python","rust","uv"],"license":"MIT","category":"dev-tools","readme_excerpt":"migrate-to-uv migrate-to-uv migrates a project to uv from another package manager. Usage Installation Supported package managers The following package managers are supported: - Poetry (including projects using PEP 621 in Poetry 2.0+) - Pipenv - pip-tools - pip More package managers (e.g., setuptools) could be implemented in the future. Features migrate-to-uv converts most existing metadata from supported package managers when migrating to uv, including: - Project metadata ( name , version , authors , ...) - Dependencies and optional dependencies - Dependency groups - Dependency sources (index, git, URL, path) - Dependency markers - Entry points Version definitions set for dependencies are also preserved, and converted to their equivalent PEP 440 for package managers that use their own syntax (for instance Poetry's caret syntax). At the end of the migration, migrate-to-uv also generates uv.lock file with uv lock command to lock dependencies, and keeps dependencies (both direct and transitive) to the exact same versions they were locked to with the previous package manager, if a lock file was found.","default_branch":null,"files":null,"tree":[],"storefront":"/r/osprey-oss","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/osprey-oss/migrate-to-uv/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}