On Nov 29, 1:41 pm, Chris Withers 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
> >> calle
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 wr
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
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.
