Is your feature request related to a problem? Please describe.
@katduecker raised a point in the course of integrating her new model that FutureWarning is recommended for deprecations that impact end-users, instead of DeprecationWarning. The latter is instead primarily intended for other Python developers, not end-users. Reading the official documentation https://docs.python.org/3/library/warnings.html#warning-categories supports what she says.
Therefore, we should change most, if not all, DeprecationWarning across hnn-core to be FutureWarning, in the cases where we want to notify USERS that anything is going to be deprecated in the future.
Is your feature request related to a problem? Please describe.
@katduecker raised a point in the course of integrating her new model that
FutureWarningis recommended for deprecations that impact end-users, instead ofDeprecationWarning. The latter is instead primarily intended for other Python developers, not end-users. Reading the official documentation https://docs.python.org/3/library/warnings.html#warning-categories supports what she says.Therefore, we should change most, if not all,
DeprecationWarningacrosshnn-coreto beFutureWarning, in the cases where we want to notify USERS that anything is going to be deprecated in the future.