Add a migration guide from pip to uv projects #12382
Draft
+277
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zanieb
force-pushed
the
zb/pip-wip
branch
2 times, most recently
from
4eb8dd6 to
1c68c8e
Compare
samypr100
reviewed
Mar 24, 2025
Comment on lines
+16
to
+18
| When using pip, requirements files specify both the dependencies for your project and lock | ||
| dependencies to a specific version. For example, if you require `fastapi` and `pydantic`, you'd | ||
| specify these in a `requirements.in` file: |
There was a problem hiding this comment.
Suggested change
| When using pip, requirements files specify both the dependencies for your project and lock | |
| dependencies to a specific version. For example, if you require `fastapi` and `pydantic`, you'd | |
| specify these in a `requirements.in` file: | |
| When using `pip` with `pip-tools`, requirements files specify both the dependencies for your project and lock | |
| dependencies to a specific version. For example, if you require `fastapi` and `pydantic`, you'd | |
| specify these in a `requirements.in` file: |
|
|
||
| ### Development dependencies | ||
|
|
||
| The requirements file format can only a single set of dependencies at once. This means if you have |
There was a problem hiding this comment.
Suggested change
| The requirements file format can only a single set of dependencies at once. This means if you have | |
| The requirements file format can only describe a single set of dependencies at once. This means if you have |
| pytest | ||
| ``` | ||
|
|
||
| Notice the base requirements are included with `-r requirements.in`. This is common, as it ensures |
There was a problem hiding this comment.
Suggested change
| Notice the base requirements are included with `-r requirements.in`. This is common, as it ensures | |
| Notice the base requirements are included with `-r requirements.in` with version constraints specified by `-c requirements.txt`. This is common, as it ensures |
| $ pip freeze > requirements.txt | ||
| ``` | ||
|
|
||
| ```text tite="requirements.txt" |
There was a problem hiding this comment.
Suggested change
| ```text tite="requirements.txt" | |
| ```text title="requirements.txt" |
|
|
||
| Here, all the versions constraints are _exact_. Only a single version of each package can be used. | ||
| The above example was generated with `uv pip compile`, but could also be generated with | ||
| `pip-compile` from `pip-tools`. The `requirements.txt` can also be generated using `pip freeze`, by |
There was a problem hiding this comment.
Suggested change
| `pip-compile` from `pip-tools`. The `requirements.txt` can also be generated using `pip freeze`, by | |
| `pip-compile` from `pip-tools`. The `requirements.txt` can also be generated using `pip freeze` on a pristine environment, by |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is incomplete, but I wanted to post it to share progress. I've finished the "how" of importing from
requirements.txttopyproject.toml. The next step is to work on the narrative and explanation of other changes.Rendered