Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better document exact requirement specification #5874

Merged
merged 3 commits into from
Jun 19, 2022
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -293,6 +293,7 @@ You also can specify a constraint when adding a package, like so:
```bash
poetry add pendulum@^2.0.5
poetry add "pendulum>=2.0.5"
poetry add "pendulum==2.0.5"
mkniewallner marked this conversation as resolved.
Show resolved Hide resolved
```

If you try to add a package that is already present, you will get an error.
Expand Down
5 changes: 4 additions & 1 deletion docs/dependency-specification.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,10 +74,13 @@ Here are some examples of inequality requirements:
### Exact requirements

You can specify the exact version of a package.

`==1.2.3` is an example of an exact version specification.

This will tell Poetry to install this version and this version only.
If other dependencies require a different version, the solver will ultimately fail and abort any install or update procedures.

#### Multiple requirements
### Multiple requirements
mkniewallner marked this conversation as resolved.
Show resolved Hide resolved

Multiple version requirements can also be separated with a comma, e.g. `>= 1.2, < 1.5`.

Expand Down