On Tue, Aug 17, 2010 at 2:07 PM, Fernando Perez <[email protected]>wrote:
> On Sat, Aug 14, 2010 at 6:11 AM, Ralf Gommers > <[email protected]> wrote: > > Installing into a local virtualenv (with either of the methods that work) > > looks good. Into /Library/Frameworks/..., nose refuses to run any tests, > due > > to the files being executable. But I think that's normal. Changing > > permissions to 644 manually it all looks good again. > > You can also pass --exe to nose to override this safety, if you want > (output of nosetests --help below): > > --exe Look for tests in python modules that are > executable. > Normal behavior is to exclude executable modules, > since they may not be import-safe [NOSE_INCLUDE_EXE] > --noexe DO NOT look for tests in python modules that are > executable. (The default on the windows platform is > to > do so.) > > Thanks, that does the trick. Tests run with "np.test(extra_argv=['--exe'])". I didn't notice at first that setuptools always does this, also for python 2.x installs through setupegg.py. Committed in r8655. Cheers, Ralf
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
