Mon May 1 10:50:59 2006

Ticket #51 (Closed: invalid)

nose.collector causes loop when running `setup.py test`

Priority: normal Reporter: support-forums4@farmdev.com
Severity: normal Assigned to: jpellerin
Component: nose Status: closed
Version: 0.9a1 Resolution: invalid
Milestone: 0.9a2 Keywords:  

Description by support-forums4@farmdev.com:

have a looksee here at my setup.py file: svn co http://svn.testtools.python-hosting.com/trunk --revision=186 testtools

I'm using test_suite = "nose.collector" and when I run `setup.py test` with 0.9a1 it gets caught in a loop like so :

running test running egg_info writing testtools.egg-info/PKG-INFO writing top-level names to testtools.egg-info/top_level.txt writing manifest file 'testtools.egg-info/SOURCES.txt' running build_ext At revision 186. running test running egg_info writing testtools.egg-info/PKG-INFO writing top-level names to testtools.egg-info/top_level.txt writing manifest file 'testtools.egg-info/SOURCES.txt' running build_ext At revision 186.

... but when I run `nosetests` everything goes smooth. I mentioned in the email that it was working on dev2, but I meant it was working for other projects. I.E. running `python setup.py test` in etl/trunk/py-lib/ works just fine. I can't see offhand what is different.

Changelog

Mon May 1 10:58:02 2006: Modified by guest

    d'oh, forgot to "preview" here is readable output of the loop : 

    running test
running egg_info
creating testtools.egg-info
writing testtools.egg-info/PKG-INFO
writing top-level names to testtools.egg-info/top_level.txt
writing manifest file 'testtools.egg-info/SOURCES.txt'
writing manifest file 'testtools.egg-info/SOURCES.txt'
running build_ext
At revision 186.
running test
running egg_info
writing testtools.egg-info/PKG-INFO
writing top-level names to testtools.egg-info/top_level.txt
writing manifest file 'testtools.egg-info/SOURCES.txt'
running build_ext
At revision 186.

    and a command to grab my setup file: 

    svn co http://svn.testtools.python-hosting.com/trunk --revision=186 testtools

    Mon May 1 17:23:13 2006: Modified by jpellerin

    • milestone set to 0.9
    • status changed from new to assigned

    Tue May 2 17:03:40 2006: Modified by jpellerin

    • milestone changed from 0.9 to 0.9a2

    Tue May 2 17:48:05 2006: Modified by jpellerin

      The problem is that nose is loading setup_devdist.py. Not sure why it *isn't* doing that when run as nosetests, but either way it suggests that nose should be automatically excluding any module with setup anywhere in the name.

      Mon May 8 21:09:03 2006: Modified by jpellerin

      • resolution set to invalid
      • status changed from assigned to closed

      nosetests is loading setup_devdist.py -- it just doesn't have a valid setup command in sys.argv, so the setup() run there does nothing.

      This isn't a nose problem per se, though it does point out the danger of putting non-import-safe modules in nose's way. See #54 for a partial solution.