Re: Import path for unit tests

2005-12-02 Thread Ben Finney
Duncan Booth <[EMAIL PROTECTED]> wrote: > Ben Finney wrote: > > What is the common idiom here? I can conceive of several possible > > ways to get around it, all of which seem hackish to some degree. > > I don't know if it is the common idiom, but I tend to write: > > TESTDIR = os.path.dirname(os.

Re: Import path for unit tests

2005-12-02 Thread Duncan Booth
Ben Finney wrote: > This works, so long as the foomodule is *not* in the path before the > appended '..' directory. When writing unit tests for a development > version of a package that is already installed at an older version in > the Python path, this fails: the unit tests are not importing the

Import path for unit tests

2005-12-02 Thread Ben Finney
Howdy all, My practice when writing unit tests for a project is to make 'test/' subdirectories for each directory containing modules I want to test. project-foo/ +-- lib/ | +-- test/ +-- data/ +-- gui/ | +-- test/ +-- server/ +-- test/ This means that I ne