Repository navigation
BUG: redundant deprecation warning #23494
Description
Activity
@seberg can correct me if I'm wrong, but I believe this is intentional. Some context is provided #22021 and the linked discussion on the mailing list. I agree it's a bit confusing without the additional context, but I'm not sure how best to improve the situation without getting too verbose.
Ah I see, thanks for the link
I searched a bit for similar open issue before opening this one, but didnt go that far in time (that issue was opnened on July 21st 2022)
I suppose it's perfectly OK to close this issue, as it's being already worked on from what I can see.
Any discussion regarding this can be had there.Yeah, I mind integrating the warning into the error message, but it was intentional to go via an error and not switch directly.
Describe the issue:
Starting in v1.20, when calling a numpy built in type prints a warning:
FutureWarning: In the future 'np.bool' will be defined as the corresponding NumPy scalar. (This may have returned Python scalars in past versions.It seems these types were dropped in v1.24, resulting in the exception:
AttributeError: module 'numpy' has no attribute 'bool'. Did you mean: 'bool_'?However, the warning is still shown. It seems redundant or incorrect in its current form.
Only the exception should be shown, or the warning text should be changed.
Reproduce the code example:
Error message:
Runtime information:
Not relevant
Context for the issue:
It's simply a confusing combination of contradicting warning and exception.
Judging by the warning type and text, it seems that the exception should not be raised (FutureWarning type and "in the future" text)