They're all doing what they're told.
I call modules like x_utils.py, where prefix x is assigned to a
particular pakage. In this case import statements look like:
import Company.repotrtools.e_excel as e_excel
or
from Company.repotrtools.e_excel import e_writer, e_reader
generally this are classes, not functions.
Newer had namespace collisions (yet :)
--
http://mail.python.org/mailman/listinfo/python-list
On Thu, Feb 17, 2005 at 06:20:36PM +, Will McGugan wrote:
> Hi,
>
> I'm accumulating a number of small functions, which I have sensibly put
> in a single file called 'util.py'. But it occurs to me that with such a
> generic name it could cause problems with other modules not written by
> my
Will McGugan wrote:
I'm accumulating a number of small functions, which I have sensibly put
in a single file called 'util.py'. But it occurs to me that with such a
generic name it could cause problems with other modules not written by
myself. Whats the best way of handling this? If I put it in a
On Thu, 17 Feb 2005 18:20:36 +, Will McGugan wrote:
> I'm accumulating a number of small functions, which I have sensibly put
> in a single file called 'util.py'. But it occurs to me that with such a
> generic name it could cause problems with other modules not written by
> myself. Whats the
Will McGugan wrote:
Hi,
I'm accumulating a number of small functions, which I have sensibly put
in a single file called 'util.py'. But it occurs to me that with such a
generic name it could cause problems with other modules not written by
myself. Whats the best way of handling this? If I put it
Hi,
I'm accumulating a number of small functions, which I have sensibly put
in a single file called 'util.py'. But it occurs to me that with such a
generic name it could cause problems with other modules not written by
myself. Whats the best way of handling this? If I put it in a common
locatio
