On Wed, 17 May 2017 at 11:03:40 +0200, Thomas Goirand wrote:
> On 05/16/2017 02:30 PM, Simon McVittie wrote:
> > PyPI packages correspond to Debian source packages, not binary packages.
>
> I don't think there ever was a source package name policy, neither in
> Debian nor in this group.
I meant c
[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 na
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 h
On 05/16/2017 02:30 PM, Simon McVittie wrote:
> PyPI packages correspond to Debian source packages, not binary packages.
I don't think there ever was a source package name policy, neither in
Debian nor in this group.
> dbus-python (upstream and) on PyPI is the source package dbus-python but
> the
4 matches
Mail list logo