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 -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco -- http://mail.python.org/mailman/listinfo/python-list
