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

Add extra solve options #586

Open
wolfv opened this issue Mar 30, 2024 · 3 comments
Open

Add extra solve options #586

wolfv opened this issue Mar 30, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@wolfv
Copy link
Contributor

wolfv commented Mar 30, 2024

uv has some nice solver options:

  • --exclude-newer (compare timestamps and exclude packages that were published after some date)
  • --override to override some dependencies (basically a way of locally "repodata patching")
@baszalmstra baszalmstra added the enhancement New feature or request label May 6, 2024
@baszalmstra
Copy link
Collaborator

baszalmstra commented May 14, 2024

exclude_newer has been implemented in #654

@baszalmstra
Copy link
Collaborator

@wolfv What do you think should be the input for --override? What would it look like in code?

@wolfv
Copy link
Contributor Author

wolfv commented May 16, 2024

I am thinking something like HashMap<MatchSpec, MatchSpec>.

So that you can do something like:

jupyterlab 3.3.*: python ==3.10

And this would replace all dependencies with name python of any jupyterlab 3.3.* with the specified one.

It's relatively broad but I think people should be able to make it specific enough for their use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants