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

From: Arnaud Delobelle <arnodel@xxxxxxxxx>
Date: Thu, 9 Feb 2012 14:36:52 +0000

On 9 February 2012 14:00, Laurent Claessens <moky.math@xxxxxxxxx> 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 avoiding name clashes with standard modules and site
packages.

Thanks.

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.

--
Arnaud
.

Follow-Ups:
- Apparent "double imports" (was: Naming convention for in-house modules (Newbie question))
  - From: HoneyMonster
- Re: Naming convention for in-house modules (Newbie question)
  - From: Laurent Claessens

References:
- Naming convention for in-house modules (Newbie question)
  - From: HoneyMonster
- Re: Naming convention for in-house modules (Newbie question)
  - From: Laurent Claessens

Prev by Date: Re: frozendict
Next by Date: Re: frozendict
Previous by thread: Re: Naming convention for in-house modules (Newbie question)
Next by thread: Re: Naming convention for in-house modules (Newbie question)
Index(es):
- Date
- Thread

Relevant Pages

Apparent "double imports" (was: Naming convention for in-house modules (Newbie question))
... for things like error handling/logging. ... but is there a recommended way of naming such ... I am concerned about avoiding name clashes with standard ... modules and site packages. ...
(comp.lang.python)
Re: Naming convention for in-house modules (Newbie question)
... for things like error handling/logging. ... but is there a recommended way of naming such modules? ... concerned about avoiding name clashes with standard modules and site ... This explain you WhatCaseToChoose for_naming youVariables. ...
(comp.lang.python)