summaryrefslogtreecommitdiff
path: root/numpy/array_api/_array_object.py
diff options
context:
space:
mode:
authorSebastian Berg <sebastian@sipsolutions.net>2022-05-05 00:16:58 +0200
committerSebastian Berg <sebastian@sipsolutions.net>2022-05-05 00:16:58 +0200
commit806d126d5f0c657ea53cf7acc6941b77960dd0a3 (patch)
tree096a43bf7245b31e388ec378a307106013cc80c9 /numpy/array_api/_array_object.py
parent5c740d0ca3d35c151c5120a551a69319ffac04d9 (diff)
downloadnumpy-806d126d5f0c657ea53cf7acc6941b77960dd0a3.tar.gz
BUG: Ensure compile errors are raised correclty
This has been bugging me for a bit. The concurrent.futures Executor requires checking the result for the error to be raised. That makes sense, but just means we need to consume the result explicitly here to ensure we know about compile errors. Otherwise, compile errors just pass silently (which is very confusing if the old object files are still around and the tests run based on the old version).
Diffstat (limited to 'numpy/array_api/_array_object.py')
0 files changed, 0 insertions, 0 deletions