Use company name for module

[Micah Carrick]

My company is working on releasing some of our code as open-source python
modules. I don't want my "foo" module conflicting with other modules called
"foo" on PyPi or github or a user's system. Is there anything wrong, from a
conventions standpoint, with having modules like company.foo and company.bar
even if foo and bar are not necessarily related other than being released by
us? I really don't like the cryptic module names or things like foo2 and the
like.

-- 
Micah Carrick - http://www.micahcarrick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20101112/bacaab96/attachment.html>