Hi, On Tue, 16 Aug 2016, Michael Ströder wrote:
Since ages the convention is that a distribution package name of a Python module should be "python-<import-name>".
The wiki says: https://en.opensuse.org/openSUSE:Packaging_Python#Naming_policy
All Python module packages, whether pure Python or C-based, should be
called python-modulename. modulename should be the name of this module on the Python Package Index, the official third-party software
This rule is actively enforced from a couple of SuSE people, that didn't accept a submission to d:l:py with a differing name, namely Sascha Peilicke.
Where and when was this discussed *before* enforcing this weird naming convention?
I guess you can discuss it now publicly. Sascha isn't with SUSE anymore, and it's not clear if anybody remembers the full reasons for that policy. FWIW: the thing the policy wants to achieve (at least that which I gather from this thread, I'm not involved or interested in python packages per se), namely having a relieable naming for python modules coming from the pypi eco-system could have been achieved just as well by enforcing the existence of one additional Provides: named funnily. No package rename (or naming policy) would have been necessary. But another thing is also true: installation routines that rely on package names are inherently flawed, there are all sorts of reasons to rename packages (and some of them are more necessary than this example here), and of course package names often differ cross distributions, while Provides are more stable or can be made so (because there can be multiple per package). So this incident also presents opportunities to fix those not well thought out installation schemes. Ciao, Michael.