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
NumPy 1.16 support #3826
NumPy 1.16 support #3826
Conversation
As title. Closes numba#3741
As title.
As title.
Morning, I'll have a look at refactoring I've tested locally on a couple of pre- and post-1.16 versions and it seems OK - so just thought I would flag it in case useful. |
numba/targets/arraymath.py
Outdated
# has dtype, but is not something understandable | ||
if 'cannot be represented' in str(e) or \ | ||
'data type not understood' in str(e): | ||
obj = obj.dtype |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the only sensible type for obj
is Sequence
. Better to explicitly check for that then to rely on exception messages.
The rest looks good. Just pending CI. |
Resolved Conflicts: docs/source/reference/numpysupported.rst numba/tests/test_np_functions.py
I've merged in master to resolve conflicts and also reenabled some more skipped np 116 tests. |
Pending CI pass I think this can be merged. |
CI looks good. |
As title.
Closes #3741