On 12-Nov-2023, Sandro Tosi wrote: > > The inconsistent constraints need to be resolved; > > no they dont. debian uses apt not pip to install packages.
The ‘pip’ command-line tool can also query which packages Python knows are installed, and that uses the database derived from Python package metadata. So, the Python metadata installed by the Debian package needs to be consistent with the dependencies. > from a packaging perspective, what matter is "does rich work?" and since > the answer is "yes" In the aspect of Python giving the correct answer from a query using ‘pip’, it isn't working. This is because the query is not of the Debian package database, but the Python metadata. This can be resolved by making the Debian dependencies and the Python metadata declared dependencies, consistent. Please address this so that the Python standard ‘pip’ tool can get the correct information from the Python metadata installed by these Debian packages. -- \ “Science is a way of trying not to fool yourself. The first | `\ principle is that you must not fool yourself, and you are the | _o__) easiest person to fool.” —Richard P. Feynman, 1964 | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
