Python naming clarification

[Michel Salim]

On 11/13/06, Toshio Kuratomi <a.badger at gmail.com> wrote:
> On Sun, 2006-11-12 at 23:47 -0500, Michel Salim wrote:
> > On 11/12/06, Jesse Keating <jkeating at redhat.com> wrote:
> > > On Sunday 12 November 2006 20:58, Michel Salim wrote:
> > > > According to the Package Naming Guidelines, python-dependent packages
> > > > should be named python-%{name}, unless the name contains py or Py. I'm
> > > > looking at packaging Django, which is a web application framework
> > > > similar to TurboGears, and I note that the latter is in Fedora under
> > > > the name of, yes, TurboGears.
> > >
> > > I thought it was python module packages that needed to be python-foo or pyfoo
> > > or foopy.  Applications that happen to be written or partially written in
> > > python are exempt from this, or so I assumed (as I just submitted and built
> > > pungi, an application that is written in python, and has its own python
> > > module (pypungi)).
> > >
> > Ah, good. I just submitted it as Django:
> >
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=215267
>
>
> Jesse is right about modules vs applications but turbogears is
> definitely a module so I would argue that TurboGears was misnamed when
> it got in.  You use TurboGears in you website using:
>   import turbogears
>
> Thus its a module with lowercase import name  so it should be named:
>   python-turbogears
>
That was my source of confusion, yes. On the other hand, both
TurboGears and Django provide scripts for managing your web
application, and in fact the interaction between the developer and the
framework is through these scripts, so perhaps they can be considered
applications?



-- 
Michel Salim

Don't worry about avoiding temptation -- as you grow older, it starts
avoiding you.
                -- The Old Farmer's Almanac