binary package names
[Thomas Goirand, 2017-05-17]
> 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?
who named the module? We didn't, upstream did.
Why do you think egg name more important than the module name?
It's used in requires.txt, right, but is this name available in the
traceback? If it is (one special case with pkg_resources) - why there
are two mechanisms? Which one is universal? How many Python libraries
provide Egg name (other than the one generated automatically since few
Python interpreter releases) and why so little? Why should we optimise
for special cases?
Are library package names for end users or developers? Which name
strategy is more useful?
The fact that Openstack uses something else and it's easier for you
doesn't meant it's easier for everyone else.
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Reply to: