oct2py hangs when called via nosetests or py.tests on python 2.7 about oct2py HOT 7 CLOSED

Hi @ocefpaf, nothing jumps out at me as you while your build would fail, unless __file__ is not what you think it is. Perhaps print the value of path so it shows up in the error report? You might also try breaking the first command into two parts, I'm not sure I've tested a nested call as the first call (though I'll go ahead and do that in light of this question).

path = os.path.join(rootpath, 'seawater_v3_3')
print(path)
genpath = octave.genpath(path)
print(genpath)
_ = octave.addpath(genpath)

from oct2py.

Thanks for the quick response!

Hi @ocefpaf, nothing jumps out at me as you while your build would fail, unless file is not what ou think it is. Perhaps print the value of path so it shows up in the error report?

Printing displays the directory as expected.

You might also try breaking the first command into two parts, I'm not sure I've tested a nested call as the first call (though I'll go ahead and do that in light of this question).

I will try that as soon as I can. But everything works as is on Python 3,
and even Python 2 if I do not call via py.test or nose.

path = os.path.join(rootpath, 'seawater_v3_3')
print(path)
genpath = octave.genpath(path)
print(genpath)
_ = octave.addpath(genpath)

from oct2py.

I meant that __file__ could be different when using a test runner.

from oct2py.

I meant that file could be different when using a test runner.

I debugged printed it while using the test runner. If I omit the line genpath = octave.genpath(path) it prints the right thing. If I run the code "as is" it hangs and nothing gets printed, not even the calls before that line! My knowledge of test runner is very limited to understand what happens under the hood.

This might not be oct2py's fault... So I am closing this until I find some time to investigate more. What puzzles me is that everything works just fine in Python3 😒

from oct2py.

I ran a similar check where the first call was nested, and it passed on Python 2.7, so I am at a loss, unless the combination of the two commands was taking longer than 3 seconds in your build...

from oct2py.

Nope, it hangs forever. The 3 seconds I introduced to avoid waiting.

from oct2py.

Darn.

from oct2py.