Python submodule naming

[Toshio Kuratomi]

Luke Macken is working on a few python packages for infrastructure and
has run across an unanticipated naming issue with python-pastedeploy and
python-pastescript[1]_.

Our present naming guidelines [2]_ say to use the name of the python
module when it is imported.  The question is how does this map to
submodules?  In this case:

  import paste.deploy
  import paste.script

This could reasonably be named python-pastedeploy or
python-paste-deploy.  Do we want to specify that submodules be named one
or the other or leave it up to the packager?

For what it's worth, Debian has python-pastedeploy but also
python-twisted-conch so they seem to leave it to the packager ATM.

[1]_
https://www.redhat.com/archives/fedora-extras-list/2006-July/msg00676.html
[2]_
http://www.fedoraproject.org/wiki/Packaging/NamingGuidelines#AddonPython

-Toshio

[Tom Callaway]

On Fri, 2006-08-18 at 12:36 -0700, Toshio Kuratomi wrote:
>  Luke Macken is working on a few python packages for infrastructure
> and
>  has run across an unanticipated naming issue with python-pastedeploy and
>  python-pastescript[1]_.
>  
>  Our present naming guidelines [2]_ say to use the name of the python
>  module when it is imported.  The question is how does this map to
>  submodules?  In this case:
>  
>    import paste.deploy
>    import paste.script
>  
>  This could reasonably be named python-pastedeploy or
>  python-paste-deploy.  Do we want to specify that submodules be named one
>  or the other or leave it up to the packager?
>  
>  For what it's worth, Debian has python-pastedeploy but also
>  python-twisted-conch so they seem to leave it to the packager ATM. 
Up to developer's discretion, IMHO. Look at what upstream calls it.

~spot
-- 
Tom "spot" Callaway: Red Hat Technical Team Lead || GPG ID: 93054260
Fedora Extras Steering Committee Member (RPM Standards and Practices)
Aurora Linux Project Leader: http://auroralinux.org
Lemurs, llamas, and sparcs, oh my!

[Toshio Kuratomi]

On Fri, 2006-08-18 at 15:10 -0500, Tom 'spot' Callaway wrote:
>  On Fri, 2006-08-18 at 12:36 -0700, Toshio Kuratomi wrote:
>  > In this case:
>  > 
>  >   import paste.deploy
>  >   import paste.script
>  > 
>  > This could reasonably be named python-pastedeploy or
>  > python-paste-deploy.  Do we want to specify that submodules be named one
>  > or the other or leave it up to the packager?
>  > 
>  > For what it's worth, Debian has python-pastedeploy but also
>  > python-twisted-conch so they seem to leave it to the packager ATM.
>  
>  Up to developer's discretion, IMHO. Look at what upstream calls it. 
Sounds good to me.  If no one objects today, I'll post that to the bugs
which are waiting for clarification (as this isn't a Guideline change
AFAIS).

-Toshio