Re: Apparent "double imports" (was: Naming convention for in-house modules (Newbie question))

2012-02-09 Thread HoneyMonster
On Thu, 09 Feb 2012 12:02:03 -0700, Ian Kelly wrote: > On Thu, Feb 9, 2012 at 11:53 AM, HoneyMonster > wrote: >> One issue I have run into, which may or may not be a problem: I am >> finding that modules in the in-house "library" package sometimes have >> to import modules like sys and os, which

Re: Apparent "double imports" (was: Naming convention for in-house modules (Newbie question))

2012-02-09 Thread Ian Kelly
On Thu, Feb 9, 2012 at 11:53 AM, HoneyMonster wrote: > One issue I have run into, which may or may not be a problem: I am > finding that modules in the in-house "library" package sometimes have to > import modules like sys and os, which are also imported by the "calling" > module. Is this a proble

Apparent "double imports" (was: Naming convention for in-house modules (Newbie question))

2012-02-09 Thread HoneyMonster
On Thu, 09 Feb 2012 14:36:52 +, Arnaud Delobelle wrote: > On 9 February 2012 14:00, Laurent Claessens wrote: >> >>> Here is my question: I would like to start an in-house library of >>> small modules to import, for things like error handling/logging. >>> That's easy enough, but is there a rec

Re: Naming convention for in-house modules (Newbie question)

2012-02-09 Thread Laurent Claessens
This is not 100% an answer to the question, but you should read that : http://www.python.org/dev/peps/pep-0008/ The OP mentions PEP 8 in the bit of his message that you *don't* quote. Well... I've to sleep. Sorry :( Laurent -- http://mail.python.org/mailman/listinfo/python-list

Re: Naming convention for in-house modules (Newbie question)

2012-02-09 Thread Arnaud Delobelle
On 9 February 2012 14:00, Laurent Claessens wrote: > >> Here is my question: I would like to start an in-house library of small >> modules to import, for things like error handling/logging. That's easy >> enough, but is there a recommended way of naming such modules? I am >> concerned about avoidi

Re: Naming convention for in-house modules (Newbie question)

2012-02-09 Thread Laurent Claessens
Here is my question: I would like to start an in-house library of small modules to import, for things like error handling/logging. That's easy enough, but is there a recommended way of naming such modules? I am concerned about avoiding name clashes with standard modules and site packages. Thank

Re: Naming convention for in-house modules (Newbie question)

2012-02-08 Thread Chris Rebert
On Wed, Feb 8, 2012 at 9:15 AM, HoneyMonster wrote: > I am quite new to Python (2.7 on Linux), and have built a few modules > using wxPython/wxGlade for GUI elements and Psycopg2 for database access. > I adhere mostly to the PEP8 guidelines, and use Pylint to help with > quality control. > > So fa

Naming convention for in-house modules (Newbie question)

2012-02-08 Thread HoneyMonster
I am quite new to Python (2.7 on Linux), and have built a few modules using wxPython/wxGlade for GUI elements and Psycopg2 for database access. I adhere mostly to the PEP8 guidelines, and use Pylint to help with quality control. So far I have been *very* impressed. Due to Python's straightforwa