`numexpr` still uses `NPY_ARRAY_UPDATEIFCOPY`
See original GitHub issueWe deprecated NPY_ARRAY_UPDATEIFCOPY a pretty long time ago, but with a Python warning. There is one (probably almost never used) branch that still has an NPY_ARRAY_UPDATEIFCOPY . NumPy main currently removes the symbol entirely, so this will not work. And if compiled on older NumPy versions, it would just do the wrong thing (not copy back).
It is in an n_inputs == 0 branch, is that branch meaningless enough, or should we fix this here, and delay the deprecation for one release in NumPy for the sake of numexpr?
Here is the code: https://github.com/pydata/numexpr/blob/d745933d1fb79f08ca152463480d506199ea24f0/numexpr/interpreter.cpp#L1271
Issue Analytics
- State:
- Created 2 years ago
- Comments:32 (15 by maintainers)
Top Results From Across the Web
NumExpr 2.0 User Guide — numexpr 2.6.3.dev0 documentation
The numexpr package supplies routines for the fast evaluation of array expressions elementwise by using a vector-based virtual machine. Using it is simple:....
Read more >NumExpr: Fast numerical expression evaluator for NumPy
NumExpr is a fast numerical expression evaluator for NumPy. With it, expressions that operate on arrays (like '3*a+4*b' ) are accelerated and use...
Read more >numexpr 2.7.1 - PyPI
NumExpr parses expressions into its own op-codes that are then used by an integrated computing virtual machine. The array operands are split ...
Read more >numexpr.evaluate("a+b",out=a) - Stack Overflow
It works, because numexpr still uses temporary arrays internally, albeit in chunk sizes of 1024 elements (or 4096 if using VML).
Read more >numexpr - Read the Docs
When an array with type uint32 is used inside NumExpr, it is internally ... However, NumExpr is not flexible enough yet so as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Alright I’ve released 2.8.3. I skipped 2.8.2 because I once again didn’t have the right description metadata for RST. Not sure how that happened, probably I didn’t pull remote changes at some point. In any case I think this is resolved, if people have trouble with the writeback please re-open.
This is broken now that numpy 1.23.0 has been released, so may warrant a new
numexprrelease?