Feature: add --lockfile flag to allow users to customize lock file name #6830
Labels
Comments
|
Can you share more details about "different users"? |
zanieb
added
needs-decision
|
I should have said "different resolution". For example, one user wants to use "highest", and another wants to use "lowest-direct". |
|
I agree that the feature would be very useful in different situations. In addition to the case that @jensqin mentioned, I personally use the |
|
Another use case is to support conflicting dependencies if/when #6981 is implemented. |
BurntSushi
added a commit
that referenced
this issue
Nov 13, 2024
This PR adds support for conflicting extras. For example, consider
some optional dependencies like this:
```toml
[project.optional-dependencies]
project1 = ["numpy==1.26.3"]
project2 = ["numpy==1.26.4"]
```
These dependency specifications are not compatible with one another.
And if you ask uv to lock these, you'll get an unresolvable error.
With this PR, you can now add this to your `pyproject.toml` to get
around this:
```toml
[tool.uv]
conflicting-groups = [
[
{ package = "project", extra = "project1" },
{ package = "project", extra = "project2" },
],
]
```
This will make the universal resolver create additional forks
internally that keep the dependencies from the `project1` and
`project2` extras separate. And we make all of this work by reporting
an error at **install** time if one tries to install with two or more
extras that have been declared as conflicting. (If we didn't do this,
it would be possible to try and install two different versions of the
same package into the same environment.)
This PR does *not* add support for conflicting **groups**, but it is
intended to add support in a follow-up PR.
Closes #6981
Fixes #8024
Ref #6729, Ref #6830
This should also hopefully unblock
dagster-io/dagster#23814, but in my testing, I
did run into other problems (specifically, with `pywin`). But it does
resolve the problem with incompatible dependencies in two different
extras once you declare `test-airflow-1` and `test-airflow-2` as
conflicting for `dagster-airflow`.
NOTE: This PR doesn't make `conflicting-groups` public yet. And in a
follow-up PR, I plan to switch the name to `conflicts` instead of
`conflicting-groups`, since it will be able to accept conflicting extras
_and_ conflicting groups.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usecase
When a project needs to have multiple lock files for different users, it is convenient to be able to rename the lockfile.
API Suggestion
Context
pdm has this feature.
The text was updated successfully, but these errors were encountered: