Comment 2 for bug 710602

(sorry for delay) -- thanks for this.. I'm just working on packaging up the new 3.7.5.1 and I can't get the tests to run

In my spec file I have:

BuildRequires: python-devel, python-unittest2

%check
%{__python} -m unittest discover

which sort of runs...

Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.KlqrIA
+ umask 022
+ cd /builddir/build/BUILD
+ cd pyephem-3.7.5.1
+ unset DISPLAY
+ /usr/bin/python -m unittest discover
----------------------------------------------------------------------
Ran 0 tests in 0.000s
OK
+ exit 0

(hey, it's efficient....)

and I get the same when running on the command line

[aelwell@pcitgtelwell pyephem-3.7.5.1]$ pwd
/var/lib/mock/fedora-rawhide-x86_64/root/builddir/build/BUILD/pyephem-3.7.5.1
[aelwell@pcitgtelwell pyephem-3.7.5.1]$ ls
build debugfiles.list debugsources.list INSTALL LICENSE-GPL PKG-INFO setup.py
COPYING debuglinks.list extensions libastro-3.7.5 LICENSE-LGPL README src
[aelwell@pcitgtelwell pyephem-3.7.5.1]$ python --version
Python 2.7.2
[aelwell@pcitgtelwell pyephem-3.7.5.1]$ python -m unittest discover

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
[aelwell@pcitgtelwell pyephem-3.7.5.1]$

if I run from src/ or below I just get errors (as the package isn't installed?)
Can you advise how I should call the unittests?

Many thanks
Andrew