-E ignored when using poetry.group

[Conchylicultor]

• OS version and name: Debian
• Poetry version: 1.2.0a2

[tool.poetry]
name = "tmp-poetry"
version = "0.1.0"
description = ""
authors = ["xyz <[email protected]>"]

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

# Bellow is the bug

[tool.poetry.dependencies]
python = "^3.9"

[tool.poetry.group.group0]
optional = true

[tool.poetry.group.group0.dependencies]
numpy = "*"

[tool.poetry.extras]
numpy_extra = ["numpy"]

Issue

When [tool.poetry.extras] is used to refer to deps defined inside [tool.poetry.group.group0.dependencies], those deps are ignored.

Reproduction instrutions:

poetry install -E numpy_extra

I would expect the command to install tmp-poetry[numpy_extra] which should install numpy. However, this silently fail to install the package:

Display:

Creating virtualenv tmp-poetry-S27UDbn2-py3.9 in ~/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies... (0.1s)

Writing lock file

Installing the current project: tmp-poetry (0.1.0)

The extra deps is ignored and not installed, poetry show will display nothing.
poetry run python -c "import numpy" will fail with ModuleNotFoundError

Note: removing the groups and using instead numpy={version="*", optional=true} will work.

[finswimmer]

Hello @Conchylicultor,

this is expected. Dependency groups and extras are different concept. You cannot mix them.

Extras are a way in thy python world to define a set of dependencies, that will bring extra functionality to your package during run time.

Dependency groups are a concept by poetry to define different set of dependency that you only need during development, like linter or testing framework.

So you must ask yourself: Do I need it this dependencies during runtime or only during development? For the first case use extras, for the later use dependency groups.

fin swimmer

[Conchylicultor]

Thanks for the fast answer, However, your answer seems to contradict the doc you linked:

Poetry provides a way to organize your dependencies by groups. For instance, you might have dependencies that are only needed to test your project or to build the documentation.
Think of dependency groups as labels associated with your dependencies: they don’t have any bearings on whether their dependencies will be resolved and installed by default, they are simply a way to organize the dependencies logically.

The doc say those deps can be used for tests but not that they have to.

Additionally, even global dependencies have a "default" group, which indicates group are not limited to developpement. From the doc:

The dependencies declared in tool.poetry.dependencies are part of an implicit default group.

Additionally, other users seems to understand like me that group and extras features are complementary features which can be used jointly:
#4842

[Conchylicultor]

At minima, poetry should raise an explicit error message. I just spend half a day trying to debug this issue.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.