Re: Usual practice: running/testing modules in a package

2008-09-03 Thread Casey
On Aug 26, 10:21 pm, Casey <[EMAIL PROTECTED]> wrote: > On Aug 12, 9:57 pm, alito <[EMAIL PROTECTED]> wrote: > > > > > A wrapper on the level up works: > > > ~/python$ cat importercaller.py > > from testpackage import config > > config.hello() > > > ~/python$ python importercaller.py > > hello > >

Re: Usual practice: running/testing modules in a package

2008-08-27 Thread Casey
On Aug 12, 9:57 pm, alito <[EMAIL PROTECTED]> wrote: > > A wrapper on the level up works: > > ~/python$ cat importercaller.py > from testpackage import config > config.hello() > > ~/python$ python importercaller.py > hello > > So, how do I run these modules without writing a wrapper script for > ea

Re: Usual practice: running/testing modules in a package

2008-08-25 Thread Gabriel Genellina
--- El dom 24-ago-08, Medardo Rodriguez (Merchise Group) <[EMAIL PROTECTED]> escribió: (please keep posting on this list) On Sun, Aug 24, 2008 at 1:18 AM, Gabriel Genellina <[EMAIL PROTECTED]> wrote: I think you misunderstood the comment. I didn't. The problem is my bad English :( I'm n

Re: Usual practice: running/testing modules in a package

2008-08-23 Thread Gabriel Genellina
En Fri, 22 Aug 2008 17:31:58 -0300, Medardo Rodriguez (Merchise Group) <[EMAIL PROTECTED]> escribió: > On Fri, Aug 22, 2008 at 1:25 PM, Gabriel Genellina > <[EMAIL PROTECTED]> wrote: >> what if __init__.py contains code? > > Thats what I usually do to solve the "problem", but for my taste it's >

Re: Usual practice: running/testing modules in a package

2008-08-22 Thread Medardo Rodriguez (Merchise Group)
On Fri, Aug 22, 2008 at 1:25 PM, Gabriel Genellina <[EMAIL PROTECTED]> wrote: > what if __init__.py contains code? Thats what I usually do to solve the "problem", but for my taste it's better to write the test code of a module inside it. The code I write in "__init__.py" is related to structures o

Re: Usual practice: running/testing modules in a package

2008-08-22 Thread Gabriel Genellina
En Fri, 22 Aug 2008 10:48:50 -0300, [EMAIL PROTECTED] <[EMAIL PROTECTED]> escribió: On 18 ago, 08:28, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote: A package is a library, meant to be imported by some other code. Your main script (or the testing code) is a program, it uses (i.e. imports)

Re: Usual practice: running/testing modules in a package

2008-08-22 Thread [EMAIL PROTECTED]
On 18 ago, 08:28, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote: > A package is a library, meant to be imported by some other code. Your main > script (or the testing code) is a program, it uses (i.e. imports) the library. You are right that a module is a library and its main use is to be importe

Re: Usual practice: running/testing modules in a package

2008-08-18 Thread Gabriel Genellina
En Wed, 13 Aug 2008 04:57:32 -0300, alito <[EMAIL PROTECTED]> escribió: > Hi all, > > I am new to using packages to group my modules. I can't figure out > how to run a module that uses relative imports without writing a > wrapper that imports that module. Everything I try it complains that > I a

Usual practice: running/testing modules in a package

2008-08-13 Thread alito
Hi all, I am new to using packages to group my modules. I can't figure out how to run a module that uses relative imports without writing a wrapper that imports that module. Everything I try it complains that I am attempting a relative import in a non-package. eg ~/python/testpackage$ ls config