sub module named setup causes unexpected error in Nose

[jpellerin]

What steps will reproduce the problem?

1. create mypackage with a submodule mypackage.setup
2. create tests in mypackage.tests
3. run nosetests from the top level directory

What is the expected output? What do you see instead?

Nose somehow thinks that the setup module is a package level fixture and
setting setup.test = False does not prevent this.

Attached is a simple test suite that reproduces the problem.

Please use labels and text to provide additional information.

Google Code Info:
Issue #: 326
Author: kumar.mcmillan
Created On: 2010-03-12T19:55:33.000Z
Closed On:

[jpellerin]

last change ate my attachment. Here is the test suite again.

Google Code Info:
Author: kumar.mcmillan
Created On: 2010-03-12T19:56:04.000Z

[jpellerin]

After discussion on mailing list, this should be a feature / enhancement.

Allow anything named setup (or teardown) to be ignored with test=False

Google Code Info:
Author: kumar.mcmillan
Created On: 2010-03-13T22:47:53.000Z

[jpellerin]

Issue 320 has been merged into this issue.

Google Code Info:
Author: [email protected]
Created On: 2011-11-25T05:35:44.000Z

[jpellerin]

The workaround is to monkey-patch ContextSuitee:

ContextSuite.moduleSetup = ('setup_module', 'setupModule', 'setUpModule', 'setupHolder', 'setUp')

See:
http://hustoknow.blogspot.com/2011/02/setting-up-django-nose-on-hudson.html

Google Code Info:
Author: [email protected]
Created On: 2011-11-28T08:53:37.000Z

[kyleabeauchamp]

I wanted to ping to see if people have come up with improved workarounds for this issue.

[wpietri]

I'm new to nose and I'm struggling to apply the workaround described above. I've also tried fiddling with various command-line options in hopes of excluding the troublesome module, but with no luck. I'll have a hard time persuading my new colleagues of the virtue of continuously running the tests if they get spurious errors, so I'd appreciate any tips.