On 05/16/2017 02:38 PM, Piotr Ożarowski wrote: > hint: Debian Python Policy §3.3 recommends module name, not > egg/dist/thecurrentnamefromlatestpep
Who are we to decide that names of packages in Debian should be different from what upstream decided? That's *very* confusing for our users. I could have done the same kind of example with egg names and package names... # sudo apt-get install python-foo-bar Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python-foobar [ ... ] While the import thing should be easy to find (ie: cat /var/lib/dpkg/info/python-foo.list once the package is installed), the egg name vs package name is a *way* more confusing. Besides this, our priority should be our users, and I am convinced that most aren't python developers. Cheers, Thomas Goirand (zigo)
