Join GitHub today
Cannot run unit tests in fresh clone #33
It happens if you are using older system Paver with new devel paver.
Workaround is to paver develop new paver in your virtualenv (or to have no paver installed and use setup.py test using attached minilib).
I cannot remember a reason why this should happen thou, so I'll take a look into that.
Well, the problem is that once console_skript is invoked via paver command, your syslib's paver is used onwards, leading to further import fun.
It can be softoffixed by playing with sys.path and reload()ing paver before invoking nosetests, but it still leads to some funny consequences when some parts are seeing some versions from some paver modules. "Solution" would probably be to inspect and reload everything, but that seems rather hacky.
Rather than hacking around, I'd say I'll mention above suggestions in docs and use them.