Repository navigation
DEP: Deprecate intent(inplace) with a VisibleDeprecationWarning due to user-facing change #30809
Description
gh-29929 changed intent(inplace) in a user-facing way, because the old way did very bad things with NumPy array internals, meaning that user data could easily be corrupted.
But it was also a possible subtle behavior change, which isn't great either. It would be good to add a VisibleDeprecationWarning on it (it can be around for a long time):
- For users, it will inform them that behavior may have changed. They should make sure to pass in an array of the correct dtype.
- For maintainers, it should say that they should (eventually) migrate to
intent(in, out).
From the user-point of view, at some point intent(inplace) could just be the same behavior as intent(in, out) (after which the warning could shift to just deprecate intent(inplace) at code generation time).
Activity
abslock128w commentedon Feb 10, 2026
Hey I'd like to work on this
ill add the visible deprecation warning
to alert the user!
we shud prolly also update the docs if it already hasnt been....
Adding a note to the f2py documentation about the deprecation if its gonna stay for long
TST: Add tests for numpygh-30809 intent(inplace) deprecation