New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cython.parallel.threadid unavailable in function arguments #3594
Comments
Not being able to assign the If you were able to assign the cython module then people would do things like:
Suddenly you've made the choice of whether |
Cython explicitly tracks usage of its own special "modules" in the |
That's true.
I gave it a go. I think the method cython/Cython/Compiler/ParseTreeTransforms.py Lines 1190 to 1193 in f0b6dc2
But when I changed |
@Celelibi As far as I can tell your "add a call to visitchildren only when the node is not a parallel directive" seems to work fine. Thanks for the pointer on what needed changing - I'm not sure why it wasn't working for you. |
@da-woods, for what it's worth, here's the log of
The test failure doesn't depend on the C or C++ backend, doesn't depend on the compiler optimizations, doesn't depend on the version of python that runs I know the tests passed on travis, but I would suggest not to dismiss this issue right away as it might be the symptom of a race condition. |
Thanks for the output. I'm quite puzzled by it though. When I compare the .c file from tests/run/parallel.pyx (i.e. the two tests that are failing) with and without my PR the only differences are due to the extra test I added. If I revert the extra test I added then So I don't know I'm afraid... I guess the PR should be treated with caution because of what you say but I really don't understand where the differences could be coming from. |
It looks like this is a valid cython code.
But this is not.
This might be just a symptom of a larger issue. Many things are not possible with the cython module when compiled with cython, compared to when run with python. Like accessing its
module
object.The text was updated successfully, but these errors were encountered: