poetry fails to resolve constraints of both python and markers #3444
Description
- 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 (
-vvvoption).
- OS version and name: windows/linux (reproduced both in windows and WSL)
- Poetry version: 1.1.4
- Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/bentheiii/4a54c1d59fe40eb87dbe31711fdf8f8f
Issue
The toml file provided fails to lock, due to a version conflict on pytype and python. The message is:
The current project's Python requirement (>=3.7,<4.0) is not compatible with some of the required packages Python requirement:
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.5, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.6, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.6, so it will not be satisfied for Python >=3.9,<4.0
- pytype requires Python <3.9,>=3.6, so it will not be satisfied for Python >=3.9,<4.0
Because no versions of pytype match >2020.06.01,<2020.6.26 || >2020.6.26,<2020.7.14 || >2020.7.14,<2020.7.20 || >2020.7.20,<2020.7.24 || >2020.7.24,<2020.7.30 || >2020.7.30,<2020.8.10 || >2020.8.10,<2020.8.17 || >2020.8.17,<2020.8.28 || >2020.8.28,<2020.9.14 || >2020.9.14,<2020.9.16 || >2020.9.16,<2020.9.24 || >2020.9.24,<2020.9.29 || >2020.9.29,<2020.10.8 || >2020.10.8,<2020.11.3 || >2020.11.3,<2020.11.12 || >2020.11.12,<2020.11.23 || >2020.11.23
and pytype (2020.6.1) requires Python <3.9,>=3.5, pytype is forbidden.
And because pytype (2020.6.26) requires Python <3.9,>=3.5, pytype is forbidden.
And because pytype (2020.7.14) requires Python <3.9,>=3.5
and pytype (2020.7.20) requires Python <3.9,>=3.5, pytype is forbidden.
And because pytype (2020.7.24) requires Python <3.9,>=3.5
and pytype (2020.7.30) requires Python <3.9,>=3.5, pytype is forbidden.
And because pytype (2020.8.10) requires Python <3.9,>=3.5
and pytype (2020.8.17) requires Python <3.9,>=3.5, pytype is forbidden.
And because pytype (2020.8.28) requires Python <3.9,>=3.5
and pytype (2020.9.14) requires Python <3.9,>=3.5, pytype is forbidden.
And because pytype (2020.9.16) requires Python <3.9,>=3.5
and pytype (2020.9.24) requires Python <3.9,>=3.5, pytype is forbidden.
And because pytype (2020.9.29) requires Python <3.9,>=3.5
and pytype (2020.10.8) requires Python <3.9,>=3.5, pytype is forbidden.
And because pytype (2020.11.3) requires Python <3.9,>=3.6
and pytype (2020.11.12) requires Python <3.9,>=3.6, pytype is forbidden.
So, because pytype (2020.11.23) requires Python <3.9,>=3.6
and dyndis depends on pytype (>=2020.06.01), version solving failed.
running also printed For pytype, a possible solution would be to set the python property to ">=3.7,<3.9", which suggests that poetry is ignoring the python property altogether (since that is the property's current value).
The file locks properly if I erase the markers property, or set it to an empty string.