[SciPy-dev] WxPython required?
Travis Vaught
travis@enthought....
Sun Jan 20 14:56:20 CST 2008
On Jan 20, 2008, at 9:36 AM, Gabriel Gellner wrote:
> Upon a recent svn update, I get this error when I run scipy.test():
>
> ======================================================================
> ERROR: Failure: <type 'exceptions.RuntimeError'>(Could not locate
> wxPython base directory.)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/usr/lib/python2.5/site-packages/nose-0.10.0b1-py2.5.egg/nose/
> loader.py", line 344, in loadTestsFromName
> addr.filename, addr.module)
> File "/usr/lib/python2.5/site-packages/nose-0.10.0b1-py2.5.egg/nose/
> importer.py", line 39, in importFromPath
> return self.importFromDir(dir_path, fqname)
> File "/usr/lib/python2.5/site-packages/nose-0.10.0b1-py2.5.egg/nose/
> importer.py", line 84, in importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
> File "/home/ggellner/lib/python/lib/python2.5/site-packages/scipy/
> weave/tests/test_wx_spec.py", line 13, in <module>
> from scipy.weave import ext_tools, wx_spec
> File "/home/ggellner/lib/python/lib/python2.5/site-packages/scipy/
> weave/wx_spec.py", line 20, in <module>
> wx_base = find_base_dir()
> File "/home/ggellner/lib/python/lib/python2.5/site-packages/scipy/
> weave/wx_spec.py", line 16, in find_base_dir
> raise RuntimeError("Could not locate wxPython base directory.")
> RuntimeError: Could not locate wxPython base directory.
>
> ----------------------------------------------------------------------
>
> Upon installing wxpython this error disappears, does this mean scipy
> depends on wxpython now?
Absolutely not. This is an issue we come across quite a bit with the
enthought tool suite packages (now 'Projects') wherein tests are not
really 'unit' tests (they are integration or functional test) and
introduce a dependency in order to test integration with another lib
or a particular interface function. There are various approaches to
solve this (different test levels comes to mind, the decorator
approach to performance tests seen on this list as well). The default
test level certainly shouldn't call this test, though.
Travis (V.)
>
>
> Gabriel
> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev@scipy.org
> http://projects.scipy.org/mailman/listinfo/scipy-dev
>
More information about the Scipy-dev
mailing list