[issue31115] Py3.6 threading/reference counting issues with `numexpr`

Mark Dickinson added the comment: Judging by the current state of https://github.com/pydata/numexpr/issues/252, it does seem as though this is resolved downstream, so probably safe to close here. Robert: feel free to reopen if I misunderstood. -- nosy: +mark.dickinson stage: ->

[issue31115] Py3.6 threading/reference counting issues with `numexpr`

Change by Serhiy Storchaka : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31115] Py3.6 threading/reference counting issues with `numexpr`

Antoine Pitrou added the comment: If, judging by https://github.com/pydata/numexpr/commit/07d9245d88759f0c3dcabd88e6edefadc3061ee3, you are really calling a bunch of C API functions without holding the GIL, then it's not surprising you may get crashes all over the place. -- nosy:

[issue31115] Py3.6 threading/reference counting issues with `numexpr`

Robert McLeod added the comment: After building with Python3.7 I was able to get a useful error message that `PyMem` functions were being called inside GIL release. I will replace these with C-equivalents and try with Python 3.6. Fatal Python error: Python memory allocator called without

[issue31115] Py3.6 threading/reference counting issues with `numexpr`

New submission from Robert McLeod: I'm working on the development branch of the `numexpr` module and I've run into some problems on Python 3.6, where I seem to get a variety of errors relating to threading or reference counting errors. This module is commonly used for accelerating NumPy code,