On Thu, 09 Feb 2012 15:05:52 -0500, Dave Angel wrote:
> On 02/09/2012 02:40 PM, HoneyMonster wrote:
>> 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
On 02/09/2012 02:40 PM, HoneyMonster wrote:
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 im
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
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
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
