@bignose still https://pagure.io/python-daemon/pull-request/75 is required...
$ sudo podman run -ti --rm alvistack/ubuntu-18.04 bash root@42a128782bbf:~# apt update && apt -y full-upgrade && apt -y install python3-dev python3-pip root@42a128782bbf:~# pip3 --version pip 21.3.1 from /usr/lib/python3/dist-packages/pip (python 3.6) root@42a128782bbf:~# pip3 install python-daemon Collecting python-daemon Downloading python_daemon-3.0.1-py3-none-any.whl (31 kB) Collecting docutils Downloading docutils-0.18.1-py2.py3-none-any.whl (570 kB) |████████████████████████████████| 570 kB 22.0 MB/s Collecting python-daemon Downloading python_daemon-2.3.2-py3-none-any.whl (34 kB) Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (from python-daemon) (59.6.0) Collecting lockfile>=0.10 Downloading lockfile-0.12.2-py2.py3-none-any.whl (13 kB) Installing collected packages: lockfile, docutils, python-daemon Successfully installed docutils-0.18.1 lockfile-0.12.2 python-daemon-2.3.2 root@42a128782bbf:~# pip3 show python-daemon Name: python-daemon Version: 2.3.2 Summary: Library to implement a well-behaved Unix daemon process. Home-page: https://pagure.io/python-daemon/ Author: Ben Finney Author-email: ben+python@benfinney.id.au License: Apache-2 Location: /usr/local/lib/python3.6/dist-packages Requires: docutils, lockfile, setuptools Required-by: root@42a128782bbf:~# pip3 list --outdated Package Version Latest Type ------------- ------- ------ ----- python-daemon 2.3.2 3.0.1 wheel
This describes a bug in the Pip dependency resolver.
Both 'python-daemon' and 'setuptools' declare their dependencies correctly in available versions from PyPI; Pip has the information available to understand which is the latest version that can be installed that satisfies those dependencies, but it fails to do so.
Metadata Update from @bignose: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
With my OBS (https://build.opensuse.org/project/show/home:alvistack ) packaging experience (i.e. at least 300+ Python related packages), this is how the pip and pypi.org community works.
People always asking for clearly define meta data and python_requires with correct supported Python version in setup.cfg/setup.py/pyproject.toml.
Moreover I could understand why pip list just quick check python_requires provided from pypi.org, in order to keep the checking logic simple and avoid recursive dependency scan which do take time and effort.
We could claim it as bug, but community seems this as feature and everyone following it and working smoothly as changes proposed with this PR.
As your reference: https://github.com/pypa/warehouse/issues/3889
With the migration to 'changelog-chug' for interrogating the Change Log at build time, merged to the 'main' branch, this issue is now resolved.