On Nov 29, 1:41 pm, Chris Withers <ch...@simplistix.co.uk> wrote: > On 12/11/2010 15:50, Robert Kern wrote: > > > > > On 11/12/10 8:12 AM, Micah Carrick wrote: > >> 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. > > > Yes, using namespace packages. You need to use `distribute` in your > > setup.py in order to accomplish this. > > >http://pypi.python.org/pypi/distribute/ > >http://packages.python.org/distribute/setuptools.html#namespace-packages > > ...or setuptools. > > ...or just pick a different naming scheme, the Pyramid guys have gone for: > > company_foo > > ...and I'm inclined to do the same. > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > -http://www.simplistix.co.uk
You might want to check with your company legal folks before adopting a naming rule base on the company name. Some companies whose names are trademarked will not allow their name to be used in certain contexts, possibly including this. (I am not a lawyer!) -- http://mail.python.org/mailman/listinfo/python-list
