On Tue, Aug 16, 2016 at 3:42 AM, Michael Ströder <michael@stroeder.com> wrote:
Todd Rme wrote:
On Sat, Aug 13, 2016 at 12:37 PM, Michael Ströder <michael@stroeder.com> wrote:
Sebastian wrote:
On 08/13/2016 10:33 AM, Michael Ströder wrote:
Any reason why so many Python module packages have the misnomer python-python-* as package names? And the set of this misnomers even grow. Why get these packages accepted then at all? 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 repository for the Python programming language.
This strange SUSE-specific rule is IMO non-sense and will cause nothing than grief. Renaming existing packages will break *lots* of existing (automated) installation routines. And what about Python modules never submitted to PyPI e.g. with their own devpi repo?
We previously used the import name, but it caused a lot of problems. There are packages that provide multiple imports, multiple packages with the same imports, packages that share imports, packages that install inside the imports of other packages, etc. The pypi package name, however, must be unique, ties in with a lot of automated tools designed to work with pypi, and works with the package names used by the distutils/setuptools requirements specifiers. So the convention was changed to work better with the rest of the python packaging ecosystem, which is focused around pypi package names.
So basically your message boils down to: Forget completely about Python modules shipped with the distribution and better use pip-based installation in virtualenv to avoid relying on random distribution changes to naming conventions.
You are talking like there is one uniform naming policy across distros that openSUSE is unilateraly violating. There isn't. For example Debian and openSUSE use "python-foo" for python 2 packages and "python3-foo" for python 3, arch uses "python-foo" for python3 packages and "python3-foo" for python 3 packages, and Fedora uses "python2-foo" for python 2 packages and "python3-foo" for python 3 packages. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org