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

--no-default-groups should be able to use with --no-group and --all-groups #10890

Open
j178 opened this issue Jan 23, 2025 · 2 comments · May be fixed by #10891
Open

--no-default-groups should be able to use with --no-group and --all-groups #10890

j178 opened this issue Jan 23, 2025 · 2 comments · May be fixed by #10891
Labels
bug Something isn't working

Comments

@j178
Copy link
Contributor

j178 commented Jan 23, 2025

Summary

The pyproject.toml file:

[project]
name = "foo"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
requires-python = ">=3.13"
dependencies = [
    "itsdangerous>=2.2.0",
]

[dependency-groups]
foo = ["iniconfig"]
bar = ["blinker"]

[tool.uv]
default-groups = ["foo"]

1. --no-group can not be used with --no-default-groups

uv tree --no-default-groups --no-group bar
error: the argument '--no-default-groups' cannot be used with '--no-group <NO_GROUP>'

Usage: uv tree --no-default-groups

Expected:
uv tree --no-default-groups --no-group bar should be equivalent to uv tree --no-group foo --no-group bar.

2. --no-default-groups has higher priority than --all-groups

uv tree --all-groups --no-default-groups
Resolved 4 packages in 13ms
foo v0.1.0
└── itsdangerous v2.2.0

Expected:
uv tree --all-groups --no-default-groups should be equivalent to uv tree --no-group foo --group bar:

uv tree --no-group foo --group bar
Resolved 4 packages in 10ms
foo v0.1.0
├── itsdangerous v2.2.0
└── blinker v1.9.0 (group: bar)

Platform

Darwin 23.6.0 arm64

Version

uv 0.5.23 (ba42467 2025-01-23)

Python version

Python 3.12.8

@j178 j178 added the bug Something isn't working label Jan 23, 2025
@j178 j178 linked a pull request Jan 23, 2025 that will close this issue
@charliermarsh
Copy link
Member

So you're saying these should be allowed, just (effectively) no-ops?

@charliermarsh
Copy link
Member

Sorry, nevermind. I think what you're saying here is correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants