You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within the above if statement, I see os.path.realpath(os.path.normcase(module_path)) when comparing to path, which is called a little earlier (in line 343)
The problem is that you can get very different results when you call os.path.realpath(os.path.normcase(<your path>)) vs. os.path.normcase(os.path.realpath(<your path>)), and as a result, the if statement returns False on Windows for me. Here is the log statement:
The suggested fix is for the if statement on L350 to call os.path.normcase(os.path.realpath(module_path)).startswith(path) to match the method order on L343. I can confirm that after making this change in the source code, all of my tests are detected by nose as expected.
The text was updated successfully, but these errors were encountered:
non-symmetric path manipulations (normcase(realpath()) vs
realpath(normcase)) caused problem with finding tests on Windows and
must be unified.
fix for issue nose-devs#1106
The issue I'm experiencing seems to be pinpointed to the following lines of code:
nose/nose/loader.py
Lines 350 to 352 in 7c26ad1
Within the above if statement, I see
os.path.realpath(os.path.normcase(module_path))
when comparing to path, which is called a little earlier (in line 343)nose/nose/loader.py
Line 343 in 7c26ad1
The problem is that you can get very different results when you call
os.path.realpath(os.path.normcase(<your path>))
vs.os.path.normcase(os.path.realpath(<your path>))
, and as a result, the if statement returns False on Windows for me. Here is the log statement:The suggested fix is for the if statement on L350 to call
os.path.normcase(os.path.realpath(module_path)).startswith(path)
to match the method order on L343. I can confirm that after making this change in the source code, all of my tests are detected by nose as expected.The text was updated successfully, but these errors were encountered: