https://bugzilla.redhat.com/show_bug.cgi?id=2264463
--- Comment #14 from Ben Beasley code@musicinmybrain.net --- (In reply to Miro Hrončok from comment #11)
...if someone makes a really good argument for it in the future.
I suppose this would matter when some Python package generates a dependency on python3dist(cramjam-cli).
Exactly. Will that ever happen? No idea.
This kind of thing already happens with python3dist(cmake) and python3dist(ninja), corresponding to https://pypi.org/project/cmake/ and https://pypi.org/project/ninja/. When Python packages generate dependencies on those, they have to be patched out and replaced with manual BuildRequires on cmake and ninja-build, respectively. Admittedly, the the PyPI projects for CMake and Ninja are more of a “hack” rather than the primary upstream distribution channel, but they *are* published “officially” by the respective upstreams. Alternatively, maybe we *should* be trying to package something that satisfies python3dist(cmake) and python3dist(ninja).