FutureWarning: AffineScalarFunc.derivatives() is deprecated.

[pmaxted]

>>> from uncertainties import ufloat
>>> a = ufloat(1,1)
>>> b = ufloat(1,1)
>>> a+b
/indus/pflm/miniforge3/envs/teb2/lib/python3.14/site-packages/uncertainties/core.py:526: FutureWarning: AffineScalarFunc.error_components() is currently an instance method. This method is deprecated. In a future release it will be replaced with an instance property by the same name. It will be accessed by AffineScalarFunc.error_components (with no parentheses).
  return float(sqrt(sum(delta**2 for delta in self.error_components().values())))
/indus/pflm/miniforge3/envs/teb2/lib/python3.14/site-packages/uncertainties/core.py:491: FutureWarning: AffineScalarFunc.derivatives() is deprecated. It will be removed in a future release.
  for variable, derivative in self.derivatives.items():
2.0+/-1.4142135623730951

uncertainties version 3.2.4
python version 3.14.2
Running on Scientific Linux but also seen on macos for the same version of uncertainties and python version 3.11.9

[newville]

@pmaxted Hm, yeah, that is unfortunate. That deprecation warning is actually correct. But it is slightly obnoxious to display that warning to users when the deprecated usage is used internally, and the "users' usage" (adding objects returned from ufloat()) is not being deprecated.

I think the best workaround is (unfortunately, again) to put

import warnings
warnings.filterwarnings('ignore', module='uncertainties')

which sort of makes the warnings something the user must deal with, and also prevents them from seeing warnings.

If each warning were issued only once per session, that would be much better. This is what warnings.filterwarnings('default', module='uncertainties') is advertised to do, and the more explicit warnings.filterwarnings('once', module='uncertainties') should do that too. I don't know why they don't, but that appears to be a common problem, so 'ignore' is needed. My view (and from seeing similar cases with other libraries) is that this means warnings in Python have little value.

[jagerber48]

Thanks for sharing this. This is unfortunate. I will look at it when I get a chance. I would hope we can suppress the warning locally so the user doesn’t have to change anything. I think we should consider yanking this release. It’s a pretty big bug if uncertainties starts spewing unhelpful warnings at the user through no fault of the user. (If the user were calling the function themselves it would be a different story.)

I don’t know if we can suppress the warning for cprivate calls but keep it for public. This is what I’ll look into.

[newville]

@jagerber48 I believe a 3.2.5 release would be needed to fix this. But I am in favor.

Deprecation warnings are a nice idea, but, in my experience, they do not really act as promised. My suggestions would be to not issue the deprecation warnings, and just document the deprecation.

[jagerber48]

@newville yes, we can do 3.2.5 release. I would like to yank 3.2.4 from pypi. There is nothing very important that users need. I would rather yank it than have a version of uncertainties out that blasts users with warnings we don't want them to get. When we're ready we can release 3.2.5. In the changelog we can explain what happened to 3.2.4 and what the current state is in 3.2.5.

I think it will take me a few days to figure out what the fix should look like in 3.2.5. I want to modify our CI so that it reveals issues like this in the future before release, but it will take some time to figure out the right way to do that.

Deprecation warnings are a nice idea, but, in my experience, they do not really act as promised. My suggestions would be to not issue the deprecation warnings, and just document the deprecation.

I'm fine to take the time to make it act like we want. I'm interested in figuring out how to make it work as a learning experience.

[newville]

@ jagerber48 If 3.2.5 were released, yanking would not be necessary. I would suggest commenting out the warnings, fixing pyproject, and releasing 3.2.5 very soon. If you want to play with the warning messages, make that 3.2.6.