On 08/16/2016 03:49 PM, Thomas Bechtold wrote:
On Sat, Aug 13, 2016 at 10:33:00AM +0200, Michael Ströder wrote:
HI!
Any reason why so many Python module packages have the misnomer python-python-* as package names? And the set of this misnomers even grow.
As mentioned in other answers, the rule is to use python-<pypi-name> as package name. And we use that rule to convert pip requirements (which refer to the pypi name and are often given from te requirements.txt file or the setup.cfg file) to rpm package names. That would be impossible when you use python-<import-name>.
Best,
Tom
Couldn't the rule simply be changed to omit the second python- if it matches exactly (including case), starting everything with python-python- is one of the sillier ideas ive heard of in recent time (from a users perspective who 99% of the time looks in the distro repo and doesn't touch pip or whatever it is. I believe Michael is talking about working with automated install scripts / documentation / spec files or anything else designed to work across distro's (if you convince redhat and debian packagers to follow the follow similar python-python- conventions you would have an argument). -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B