Closed jdinunzio closed 2 years ago
cc @dimbleby @radoering -- I lack the expertise to tell if Poetry is generating reasonable constraints here (or if we're allowing something through constraints we should not)
The root cause seems to be the version constraints imposed in beta packages
duplicate #6519, fixed at https://github.com/python-poetry/poetry-core/pull/475
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.
-vvv
option) and have included the output below.Issue
Step to reproduce:
poetry install; poetry build
. The library will be built successfully, and the dependency version will be constraint with'opentelemetry-instrumentation-logging>=0.34b0,<0.34'
.Expected behaviour:
The library will be successfully installed or added.
Actual Behaviour:
The library will fail to install, since it can't satisfy the constraints of the given dependency (
'opentelemetry-instrumentation-logging>=0.34b0,<0.34'
in the above example).Comments
The root cause seems to be the version constraints imposed in beta packages, since pip install equally fails at installing a package greater than beta but less than the version:
Nevertheless, since poetry was able to install the dependency while building the library, and poetry converted the
^
dependency spec in a range, the expectation is that such range should be able to be fulfilled later.Possible solutions:
nn.mmbn
less thannn.mm
.Error log
When trying to add the library as a dependency in another poetry project: