[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian Python Policy [draft]

Neil Schemenauer <nas@python.ca> writes:

> 2.3. Module Package Names
> -------------------------
>      Python module packages should be named for the primary module
>      provided.  The naming convention for module `foo' is `python-foo'.
>      Packages which include multiple modules may additionally include
>      provides for those modules using the same convention.

What happened to the libfoo-python idea (for consistency with the perl
and, presumably, java convention)?  I'm personally happy with python-foo, but
understand the arguments in favor consistency.

Is there good reason not to adopt that now?

Reply to: