Skip to content
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

BUG: Fix numba DUFuncs added loops getting picked up #21139

Merged
merged 1 commit into from Mar 3, 2022

Conversation

charris
Copy link
Member

@charris charris commented Mar 2, 2022

Backport of #21113.

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

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 numpygh-20735
@charris charris added 00 - Bug 08 - Backport Used to tag backport PRs labels Mar 2, 2022
@charris charris added this to the 1.22.3 release milestone Mar 2, 2022
@charris charris merged commit 09a3791 into numpy:maintenance/1.22.x Mar 3, 2022
@charris charris deleted the backport-21113 branch March 3, 2022 01:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
00 - Bug 08 - Backport Used to tag backport PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants