Re: Inconsistency in source package naming for python modules
Thomas Goirand wrote:
> On 07/11/2013 09:07 PM, Stuart Prescott wrote:
>>
>>> Oh, I need this pyX package... Let's download it.
>>
>> You're using a python module name because you need to import it. If you
>> want to import modules, you want the binary package name; if you want to
>> work on the source package then you need *either* the binary package name
>> or the source package name as others have already pointed out. Knowledge
>> of source package names isn't required.
>
> But if you have py<whatever> (let's say on pypi), then even the binary
> package isn't obvious. It could be:
> python-py<whatever>
>
> or:
> python-<whatever>
>
> I've seen both cases in the archive!
and changing source package names isn't going to solve that either. There is
no convention in python-land to only have one top-level module name per
project in the namespace and to name your project after that top-level
module. At that point, the unification of namespaces between pypi (or any of
the other multitude of module repositories), source packages and binary
packages becomes impossible. As Paul indicated, this is a difficult problem
with a different solution.
--
Stuart Prescott http://www.nanonanonano.net/ stuart@nanonanonano.net
Debian Developer http://www.debian.org/ stuart@debian.org
GPG fingerprint BE65 FD1E F4EA 08F3 23D4 3C6D 9FE8 B8CD 71C5 D1A8
Reply to: