> On Nov 29, 2019, at 01:28, Simon McVittie <[email protected]> wrote: > > Is there consensus that the top-level module name is what matters, and not > following the recommendation is a bug? > https://www.debian.org/doc/packaging-manuals/python-policy/module_packages.html > says "The binary package for module foo should preferably be named > python3-foo, if the module name allows" and "import foo should import > the module", which suggests that it is indeed the name of the top-level > importable module, and not the name of the egg, that matters (which would > imply that -dbus and -gi are correct, and -pypubsub is not).
If the module name has upper case in it, it would actually break Policy §5.6.1 For example one of my package has module name fontParts, and if folllowing Python policy, the name would be python3-fontParts, and it would be a policy violation. So it has to be using all lower-case name, therefore running tests generated by autopkgtest fails. I have to generate the testing script manually and modify accordingly. Yao Wei (This email is sent from a phone; sorry for HTML email if it happens.)
