Nose incorrectly reloads a module during test finding

[jpellerin]

What steps will reproduce the problem?

1. Unpack the attached <noseimportbug.tgz> file
2. Run it with "python -m run -v --with-doctest" (in the noseimportbug directory)
3. The test failes with: AttributeError: 'NoneType' object has no attribute 'path'

What is the expected output? What do you see instead?
Expected the test to succeed as the code only calls "sys.path". However
the imported module has been set to "None"

What version of the product are you using? On what operating system?

• nose version 0.11.1
• linux and OS X

Please provide any additional information below.
The nose imported reloads a module, this is fine for test modules but
for code modules with dependencies it may fail.

In this test case the module should not even be reloaded. The nose importer
incorrectly determines the module to be not the same as the file.

In the Importer class of the "nose.importer", the "sameModule" method now has a line:

new_path = os.path.dirname(os.path.normpath(filename))

This should probably be replaced with:

new_path = os.path.dirname(os.path.normpath(os.abspath(filename)))

As it is compared with absolute paths.

Google Code Info:
Issue #: 356
Author: post4ar...@gmail.com
Created On: 2010-07-29T11:06:26.000Z
Closed On:

[jpellerin]

I've included a patch that solves this specific testcase (by adding os.abspath)

Google Code Info:
Author: post4ar...@gmail.com
Created On: 2010-07-29T11:28:20.000Z

[jpellerin]

Unfortunately this bug is still in nose version 1.0.0

BTW: os.abspath should be os.path.abspath

Google Code Info:
Author: post4ar...@gmail.com
Created On: 2011-06-14T08:58:51.000Z

[jpellerin]

Thanks. If you want to check out DEVELOPERS.txt and convert your suite to a regression test then we can integrate it quicker.

Google Code Info:
Author: kumar.mcmillan
Created On: 2011-06-14T15:15:11.000Z

[cjerdonek]

I also encountered this issue. It was very hard to understand why it was happening. For example, you can have this simple module in your package:

# foo.py
class Foo(object):
    def __init__(self):
        print Foo.__name__

Then running nose with this command (invoking nose programmatically inside start.py)--

python -m project.start --with-doctest

Would generate this error:

> python -m project.start --with-doctest
E
======================================================================
ERROR: test (project.test_file.TestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "project/test_file.py", line 7, in test
    main()
  File "project/bar.py", line 4, in main
    Foo()
  File "project/foo.py", line 3, in __init__
    print Foo.__name__
AttributeError: 'NoneType' object has no attribute '__name__'

----------------------------------------------------------------------
Ran 1 test in 0.009s

FAILED (errors=1)

It's as if all values in the global symbol table globals() for Foo's module are set to None when calling Foo(). (Even the module variable Foo has value None inside Foo.__init__.) The error does not happen when the --with-doctest flag is not passed.

[stdavis]

I'm experiencing this same issue when trying to use nose.importer:Importer in one of my projects. Is there any workaround?