Python package naming guidelines

[Timothy Selivanow]

On Fri, 2008-04-25 at 10:25 -0700, Kyle VanderBeek wrote:
> On Fri, Apr 25, 2008 at 09:02:38AM -0700, Timothy Selivanow wrote:
> > So, under that logic, I should have named pysvn python-pysvn?  That
> > seems a bit redundant to me, but I'm willing to play along if that is
> > the consensus.  From now on, I'll make an effort to name things that
> > way, unless I hear a better reason not to (name space pollution,
> > lib-{package} naming in other distros, other historical reason that I'm
> > not aware of or privy to...).
> 
> I agree that python-pysvn seems redundant, but that is the fault of the
> project creators, and is probably not up to packagers to correct. 
> Naming a python package with "py" in the name is redundant itself.  But,
> since you're going to have to "import pysvn", you might was well be
> installing python-pysvn.

Since I didn't make the deadline to have it included in F9, how
difficult/frowned upon is it to change the package name.  However, it is
in F8 now...


--Tim
 _____________________________________________________________________________ 
< "See - the thing is - I'm an absolutist.  I mean, kind of ... in a way ..." >
 ----------------------------------------------------------------------------- 
  \
   \   \
        \ /\
        ( )
      .( o ).