https://bugzilla.redhat.com/show_bug.cgi?id=1900858
code(a)musicinmybrain.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(code@musicinmybra |
|in.net) |
--- Comment #2 from code(a)musicinmybrain.net ---
That’s an interesting question. I only stumbled on this detail for fontforge
while studying dependencies for gftools (Google Fonts Tools).
In response to your question, I wrote a script, to be attached as
possible-missing-py_provides.py, to look for packages that might be in a
similar situation. It takes a long time to run, but I was not in a hurry.
The result is to be attached as possible-missing-py_provides.txt.
Importantly, this list is just based on a heuristic and probably has quite a
lot of false positives. For example, some of these Python modules or packages
might be designed only to support a particular application. While the Fedora
guidelines do not call out this case as an exception, it doesn’t seem useful to
worry about cases where the Python module or package does not provide a public
API, i.e., is not designed to be imported by code outside the application. For
example, yamllint provides a Python package of the same name, but
https://yamllint.readthedocs.io/en/stable/quickstart.html does not advertise a
Python API. Manual review of documentation is required to identify such cases.
A lot of cases in this list are those where the module name on PyPI is not the
same as the imported module, which is a case the guidelines specifically talk
about:
For any module foo intended to be used in Python 3 with import foo,
the package that includes it should provide python3-foo. This is of course always the case
if the subpackage is named python3-foo (as in the examples below). If the subpackage has
some other name, then Provides: python3-foo should be added explicitly (via %py_provides
python3-foo, see below).
For example, python3-sphinx-notfound-page provides a Python package of the same
name (sphinx-notfound-page on PyPI), and python3dist(sphinx-notfound-page) and
so on, but the package that is imported is simply named notfound, so by my
reading of the guidelines it should have %py_provides python3-notfound.
--
You are receiving this mail because:
You are on the CC list for the bug.