-
Notifications
You must be signed in to change notification settings - Fork 212
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
support new numpy complex types #458
Comments
Can you please provide a snippet of code? I'm unfamiliar with this numpy's new feature T_T. |
numpexpr fails to compile with the numpy default branch. I think this change won't go out in stable release until numpy 2 |
It's not a new feature, the NumPy main branch just tries to use the C99/C++11 definitions for complex. And those don't define Since I bet you know that you have complex doubles, could probably just not use the NumPy types at all (so that you can use C++ EDIT: But Thomas gave all the links to get an idea of how to best change it! |
thanks I’ll try to fix this
…On Wed, 29 Nov 2023 at 15:16, Sebastian Berg ***@***.***> wrote:
It's not a new feature, the NumPy main branch just tries to use the
C99/C++11 definitions for complex. And those don't define ->real and
->imag so you need to replace it.
Since I bet you know that you have complex doubles, could probably just
not use the NumPy types at all (so that you can use C++ .real() and
.imag() no matter which NumPy it is) otherwise may need to cast or use
some macro magic.
—
Reply to this email directly, view it on GitHub
<#458 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A33BDH3IIPX6TTO6XIGBP5DYG47STAVCNFSM6AAAAAA7TGV4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZRHE3TQOBQGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Closed by #461 |
With numpy main compliing numexpr fails with (a lot) of errors that look like:
I suspect the fix looks like scipy/scipy#18975 and is also a result of numpy/numpy#24085 / numpy/numpy#20880
The text was updated successfully, but these errors were encountered: