When I do: $ git clone https://salsa.debian.org/python-team/packages/poetry.git $ poetry build
I get two files in dist/ : poetry-1.1.12-py2.py3-none-any.whl and poetry-1.1.12.tar.gz According to a docstring in dh_python [1], I think the METADATA file in the .whl file is used to extract the poetry dependencies. The dependencies are the same in the generated wheel and the current 1.1.13.tar.gz downloadable on pypi.org (https://pypi.org/project/poetry/#files): Requires-Dist: cachecontrol[filecache] (>=0.12.4,<0.13.0); python_version < "3.6" Requires-Dist: cachecontrol[filecache] (>=0.12.9,<0.13.0); python_version >= "3.6" and python_version < "4.0" [...] If it's not the same, the extra-dependencies in the file setup.py in the tar.gz are the same in the current 1.1.13.tar.gz downloadable on pypi.org (https://pypi.org/project/poetry/#files): extras_require = \ {':python_version < "3.6"': ['cachecontrol[filecache]>=0.12.4,<0.13.0'], ':python_version < "3.8"': ['importlib-metadata>=1.6.0,<2.0.0'], ':python_version >= "2.7" and python_version < "2.8"': ['typing>=3.6,<4.0', 'pathlib2>=2.3,<3.0', 'futures>=3.3.0,<4.0.0', 'glob2>=0.6,<0.7', 'functools32>=3.2.3,<4.0.0', 'keyring>=18.0.1,<19.0.0', 'subprocess32>=3.5,<4.0'], ':python_version >= "3.5" and python_version < "3.6"': ['keyring>=20.0.1,<21.0.0'], ':python_version >= "3.6" and python_version < "4.0"': ['crashtest>=0.3.0,<0.4.0', 'cachecontrol[filecache]>=0.12.9,<0.13.0', 'keyring>=21.2.0,<22.0.0']} I see a difference between the 'cachecontrol' dependency and the other ones: the '[filecache]' appended to the 'cachecontrol' name. I wonder if an erroneous parsing of 'x[y]' could be part of the bug, however I would be surprised if we did not find such a problem before. 1: https://salsa.debian.org/python-team/tools/dh-python/-/blob/master/dhpython/pydist.py#L515 -- Stéphane
