Open Olegt0rr opened 2 years ago
I do use [tool.poetry.dev-dependencies]
for release tools, but the coverage
is part of an test
extras, not the main eyeD3 deps.
@nicfit I'm not familiar how the dependencies are setup but coverage is indeed getting installed by default.
$ python3 -m pip install eyed3
Collecting eyed3
Using cached eyed3-0.9.7-py3-none-any.whl (246 kB)
Collecting filetype<2.0.0,>=1.0.7
Using cached filetype-1.2.0-py2.py3-none-any.whl (19 kB)
Collecting coverage[toml]<6.0.0,>=5.3.1
Using cached coverage-5.5-cp310-cp310-macosx_10_14_x86_64.whl (207 kB)
Collecting deprecation<3.0.0,>=2.1.0
Using cached deprecation-2.1.0-py2.py3-none-any.whl (11 kB)
Collecting toml
Using cached toml-0.10.2-py2.py3-none-any.whl (16 kB)
Collecting packaging
Using cached packaging-23.0-py3-none-any.whl (42 kB)
Installing collected packages: filetype, toml, packaging, coverage, deprecation, eyed3
Successfully installed coverage-5.5 deprecation-2.1.0 eyed3-0.9.7 filetype-1.2.0 packaging-23.0 toml-0.10.2
[notice] A new release of pip available: 22.2.1 -> 23.0.1
[notice] To update, run: pip install --upgrade pip
How can I not get coverage installed as part of eyed3 since you mention that is part of test
extras?
Since test dependencies is located in
[tool.poetry.dependencies]
, poetry trying to resolve they. Even they are optional. https://github.com/nicfit/eyeD3/blob/3c073bb27db0ca2078037fe566fb9631aae094b9/pyproject.toml#L65-L72So. Let's get any application with
coverage v6
...Try to add eyed3:
And get exception:
To avoid this behaviour
eyed3
should locate dev dependencies into[tool.poetry.dev-dependencies]
instead of[tool.poetry.dependencies]
.