Closed waketzheng closed 2 months ago
I have the same issue. Can someone please provide an explanation? What does it mean? Why is the script complaining about package dependencies? Is there a workaround? Thank you for your response.
It seems that it is caused by multiple Python version definitions of the dependency like this.
numpy = [
{ version = "^1.19", python = "^3.8" },
{ version = "^1.21", python = "^3.9" },
{ version = "^1.23", python = "^3.10" },
{ version = "^1.25", python = "^3.11" },
]
When I remove the multi-version support from my package, I am able to run the export without any issues.
I'm closing this as duplicate of #176 / #183. There is a PR that will fix this issue: #286
$ poetry export --with=dev --without-hashes -o dev_requirements.txt
The
opencv-python
package has the following compatible candidates[Package('opencv-python', '4.8.1.78')]
; but, the exporter dependency walker previously electedopencv-python (4.9.0.80)
which is not compatible with the dependencyopencv-python (>=4.8,<4.9)
. Please contribute topoetry-plugin-export
to solve this problem.Versions
$ python -V
$ poetry --version
$ poetry self show plugins
Reproduce
$ cat pyproject.toml
$ cat poetry.lock
$ tree . (directory was created by
poetry new export_test
and only pyproject.toml and poetry.lock changed)