summaryrefslogtreecommitdiff
path: root/numpy/array_api/_constants.py
diff options
context:
space:
mode:
authorSebastian Berg <sebastian@sipsolutions.net>2022-02-23 14:25:50 -0800
committerSebastian Berg <sebastian@sipsolutions.net>2022-02-25 18:39:40 -0800
commit454ffba2a54449812c442852b31ec7026aff4d0f (patch)
tree7985754b6469a71c92400ed14c08b778010c3db8 /numpy/array_api/_constants.py
parent73e48ae177c4b29cdbdbcfd39e22cf5de6c7f125 (diff)
downloadnumpy-454ffba2a54449812c442852b31ec7026aff4d0f.tar.gz
BUG: Fix numba DUFuncs added loops getting picked up
It was always my intention to do this: If no loop is found and we go into the legacy ufunc path and legacy resolving works, we need to double check that the ufunc was not mutated. Normal operation never mutates ufuncs (its really not meant to be) but numbas DUFuncs need to do it (they compile loops dynamically). The future is much brighter for them in this regard, but right now they have to keep working. Closes gh-20735
Diffstat (limited to 'numpy/array_api/_constants.py')
0 files changed, 0 insertions, 0 deletions