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

Poetry reads pypi dependencies' dependencies with epoch version as <empty> #5374

Closed
3 tasks done
ashleysommer opened this issue Mar 29, 2022 · 1 comment · Fixed by python-poetry/poetry-core#316
Closed
3 tasks done
Labels
area/solver Related to the dependency resolver kind/bug Something isn't working as expected

Comments

@ashleysommer
Copy link

  • I am on the latest Poetry version.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

Issue

Installing a package named "cylc-flow" with version "8.0rc2" from pypi.

The package has a dependency that looks like metomi-isodatetime>=1!2.0.2, <1!2.1.0

But poetry seems to resolve this dependency as <empty>.

Even pinning the version of metomi-isodatetime in my own pyproject.toml file doesn't help, see the attached gist for my sample pyproject.toml file.

Loading configuration file /home/me/.config/pypoetry/config.toml
Loading configuration file /home/me/CODE/Other/Cylc-test/poetry.toml
Using virtualenv: /home/me/CODE/Other/Cylc-test/.venv
Updating dependencies
Resolving dependencies...
   1: fact: my-test is 0.0.1
   1: derived: my-test
   1: fact: my-test depends on cylc-flow (8.0rc2)
   1: fact: my-test depends on metomi-isodatetime (1!2.0.2)
   1: selecting my-test (0.0.1)
   1: derived: metomi-isodatetime (==1!2.0.2)
   1: derived: cylc-flow (==8.0rc2)
PyPI: 1 packages found for metomi-isodatetime 1!2.0.2
PyPI: 1 packages found for cylc-flow 8.0rc2
   1: selecting metomi-isodatetime (1!2.0.2)
   1: fact: cylc-flow (8.0rc2) depends on aiofiles (>=0.7.0,<0.8.0)
   1: fact: cylc-flow (8.0rc2) depends on ansimarkup (>=1.0.0)
   1: fact: cylc-flow (8.0rc2) depends on async-timeout (>=3.0.0)
   1: fact: cylc-flow (8.0rc2) depends on colorama (>=0.4,<=1)
   1: fact: cylc-flow (8.0rc2) depends on graphene (>=2.1,<3)
   1: fact: cylc-flow (8.0rc2) depends on jinja2 (>=2.11.0,<2.12.0)
   1: fact: cylc-flow (8.0rc2) depends on metomi-isodatetime (<empty>)
   1: fact: cylc-flow (8.0rc2) depends on protobuf (>=3.19.0,<3.20.0)
   1: fact: cylc-flow (8.0rc2) depends on psutil (>=5.6.0)
   1: fact: cylc-flow (8.0rc2) depends on pyuv (>=1.4.0,<1.5.0)
   1: fact: cylc-flow (8.0rc2) depends on pyzmq (>=22.0.0,<23.0.0)
   1: fact: cylc-flow (8.0rc2) depends on setuptools (>=49)
   1: fact: cylc-flow (8.0rc2) depends on urwid (>=2.0.0,<3.0.0)
   1: fact: cylc-flow (8.0rc2) depends on markupsafe (<2.1)
   1: derived: markupsafe (<2.1)
   1: derived: urwid (>=2.0.0,<3.0.0)
   1: derived: setuptools (>=49)
   1: derived: pyzmq (>=22.0.0,<23.0.0)
   1: derived: pyuv (>=1.4.0,<1.5.0)
   1: derived: psutil (>=5.6.0)
   1: derived: protobuf (>=3.19.0,<3.20.0)
   1: conflict: cylc-flow (8.0rc2) depends on metomi-isodatetime (<empty>)
   1: ! cylc-flow (==8.0rc2) is satisfied by cylc-flow (==8.0rc2)
   1: ! which is caused by "my-test depends on cylc-flow (8.0rc2)"
   1: ! thus: metomi-isodatetime is required
   1: ! not metomi-isodatetime (<empty>) is satisfied by metomi-isodatetime (==1!2.0.2)
   1: ! which is caused by "my-test depends on metomi-isodatetime (1!2.0.2)"
   1: ! thus: version solving failed
   1: Version solving took 0.162 seconds.
   1: Tried 1 solutions.

I updated to poetry-core v1.1.0a7 because it said it supports PEP440 epoch versions, but didn't seem to help.
Also updated to poetry v1.2.0b1 to get latest poetry fixes, but again didn't help.

Related to #5030
Related to python-poetry/poetry-core#264

@ashleysommer ashleysommer added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Mar 29, 2022
@finswimmer finswimmer added the area/solver Related to the dependency resolver label Mar 31, 2022
@mkniewallner mkniewallner removed the status/triage This issue needs to be triaged label Jun 11, 2022
Copy link

github-actions bot commented Mar 1, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/solver Related to the dependency resolver kind/bug Something isn't working as expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants