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
-- http://mail.python.org/mailman/listinfo/python-list
