naming conventions (and an intro)

[Toshio Kuratomi]

Kyle VanderBeek wrote:
> I couldn't find a naming convention set in the wiki, so I'll ask here.  
> As I prep the bits and pieces for packaged pylons on Fedora, I'm seeing 
> a lot of varied package names and project names.  Projects like Pylons 
> and Mako refer to themselves with caps, but provide PEP-8 friendly 
> lowercase package names, and I'm wondering how we should map these to 
> package names.
> 
> Personally I'd rather not see a package named "Mako" since it is 
> meaningless outside the context of python and provides nothing in 
> /usr/bin.  I'd probably name the package python-mako to make it sort 
> near python-*, which seems to be fairly common in Fedora and RedHat.  
> Does that sound right to you all?
> 
http://fedoraproject.org/wiki/Packaging/NamingGuidelines#AddonPython

So if mako is the name of the module you import you'd name it python-mako.

> By the way, I'm Kyle VanderBeek, professional software developer for
> IronPort (a Cisco Company).  I've been doing software development for
> more than a decade now, as well as administering a variety of Unix
> systems including RedHat/RPM Linux distros going back to 4.0 (no, not 
> RHEL 4; actual RedHat Linux 4.0).  I currently do the majority of my 
> work in Python, writing massive email anti-spam and reputation systems 
> to protect your mom's Inbox.
> 
Cool, it looks like we started using Red Hat at about the same time!

-Toshio

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.fedoraproject.org/pipermail/python-devel/attachments/20080403/ad0b4eb1/attachment.bin