5

I first noticed the problem with this project when I loaded it into Jenkins. More puzzlingly, I've been able to reproduce it as follows:

In original version of the project, the following command runs tests as expected:

.venv/bin/python setup.py nosetests

I then do the following:

  1. Clone project: hg clone my-project my-project-clone
  2. Create virtualenv .venv in clone
  3. Install requirements from cloned pip freeze file

If I then run .venv/bin/python setup.py nosetests on this version and I get the following result:

setup.py: error: Invalid command nosetests

setup.py includes the following settings:

setup_requires=[
    'nose>=1.0', 'nosexcover', 'coverage', 'selenium', 'fixture'
],
test_suite='nose.collector',

I'm especially baffled because it's the same setup.py and setup.cfg files in each version and, as far as I been able to discern, the environments are identical.

Addendum

I noticed this Stack Overflow question in the sidebar, which looks closely related, but none of the solutions offered there are working in my case.

Community
  • 1
  • 1
klenwell
  • 6,978
  • 4
  • 45
  • 84
  • Is `nose` installed in your virtualenv? i.e. can you, say, run `nosetests` from the shell inside of your virtualenv? – tom Feb 19 '13 at 23:06
  • @tom `nose` is not installed in the original version of my project. I did try installing it in the cloned version with both `pip` and `easy_install`, such that I could run `.venv/bin/nosetests`, but neither solved my issue. – klenwell Feb 19 '13 at 23:35
  • I tried running `.venv/bin/python setup.py nosetests -V` on both versions of project. Original outputs `setup.py version 1.1.2`. Cloned version: `setup.py version 1.2.1`. – klenwell Feb 19 '13 at 23:37

2 Answers2

2

I ran into the same problem and managed to fix it by putting 

setup_requires=['nose>=1.0']

Into my setup.py file. After that the Python setup.py nosetests option was available to me.

Some links that were helpful:

Adam Matan
  • 128,757
  • 147
  • 397
  • 562
user2411718
  • 81
  • 3
1

I never figured out the underlying issue exactly. But I did figure out a workaround that allowed me to get my build running. This is the command I used in the Virtualenv Builder on Jenkins:

# require nosetests be installed
# (old method using setup.py nosetests command does not work)
$VIRTUAL_ENV/bin/pip install nose

# install remain pip requirements
$VIRTUAL_ENV/bin/pip install -r requirements.pip

# must run this prior to running tests to install other nosetest dependencies
$VIRTUAL_ENV/bin/python setup.py install

# now we can run nosetests
# this does not work: $VIRTUAL_ENV/bin/python setup.py nosetests
$VIRTUAL_ENV/bin/nosetests -c setup.cfg

I suspect the root problem has to do with the state of the virtual environment and some kind of version incompatibility between Distutils and Nose in my new virtualenv. The old one seems to have arrived at a certain precarious configuration over time which cloning and pip alone cannot recreate.

klenwell
  • 6,978
  • 4
  • 45
  • 84