pipenv-uv-migrate
This is simple migration script, migrate pipenv to uv.
🚀 Get Started
Installation
$ uv tool install pipenv-uv-migrate
# -- or --
$ pipx install pipenv-uv-migrate
Migration
Step 1: Create pyproject.toml file
$ uv init
Step 2: Migrate
To migrate Pipfile to pyproject.toml.
$ pipenv-uv-migrate -f Pipfile -t pyproject.toml
When want to run dry-run mode:
$ pipenv-uv-migrate -f Pipfile -t pyproject.toml -n
Dry-run mode is pyproject.toml file does not overwrite, results are displayed on standard output.
Step 3: Generate lock file
$ uv lock
If there is already a uv.lock file, remove it first.
Step 4: Installing dependencies
To install the defined dependencies for your project.
$ uv sync
Example output
This is an example of a Pipfile to be migrated.
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[packages]
requests = "*"
[dev-packages]
pytest = ">=5.2"
Migrate the above file to the following pyproject.toml.
[project]
name = "migrate-sample"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
authors = [
{ name = "Yoshiyuki HINO", email = "yhinoz@gmail.com" }
]
requires-python = ">=3.9"
dependencies = []
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
By executing this script, pyproject.toml is rewritten as follows.
[project]
name = "migrate-sample"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
authors = [
{ name = "Yoshiyuki HINO", email = "yhinoz@gmail.com" }
]
requires-python = ">=3.9"
dependencies = [
"requests",
]
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
[dependency-groups]
dev = [
"pytest>=5.2",
]
🤝 Contributing
- Fork and clone the repository, and create the development branch.
- Run
uv syncto setup your develop environment. - Do your code.
- Run
uvx --with tox-uv tox@latestto check that your test passed. - Run
bash scripts/format.shandbash scripts/lint.shto check that you haven't warnings. - Open a PR on GitHub.
Test cases
Test cases are in tests/testdata/toml, update Pipfile with additional entries and expect_pyproject.toml with expected output.
📝 License
Metadata
Release files for pipenv-uv-migrate 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pipenv_uv_migrate-0.4.0.tar.gz | 20.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pipenv_uv_migrate-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.0 kB
Release files / pipenv_uv_migrate-0.4.0.tar.gz
| Download URL | pipenv_uv_migrate-0.4.0.tar.gz |
|---|---|
| Size | 20.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b064138242563552a7397e9dbaf5c440286233eb083f2ebea73eea40342adee4
|
|
BLAKE2b-256 checksum How to use checksums |
8b49593c3ecbbfae4062654632b397aa4789bdc20fdbe480a46b90b9dfd8ef2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 13, 2026.
Transparency logRelease files / pipenv_uv_migrate-0.4.0-py3-none-any.whl
| Download URL | pipenv_uv_migrate-0.4.0-py3-none-any.whl |
|---|---|
| Size | 14.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e240ce9f5e07c68454cd053e497c6885a75e65a6a4acfcddb9a78bddeebf5ce
|
|
BLAKE2b-256 checksum How to use checksums |
209b5a6db92184311a769dd91077c3237ad7fe9610be14ea94a664e274d1ec9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 13, 2026.
Transparency log