El 7/6/25 a las 22:32, Santiago Vila escribió:
Is this "debugging left over" related to the current failure
of CI tests which I see here?
https://tracker.debian.org/pkg/uncertainties
I'll answer myself: No, the breakage between lmfit-py and uncertainties
seems to happen because of this overly strict test which upstream has removed
recently:
https://github.com/lmfit/lmfit-py/commit/f4c5a83f6259fc46ab76f5d75de2537ba9d72b0a
I can't fix that retroactively in the testing version of lmfit-py,
so my current plan will be to drop such test in the next upload
(where I will also remove the debugging cruft) and then ask you RT for
a hint (since this is some sort of chicken-and-egg problem).
( I withdraw my idea that uncertainties should be fixed first ).
Thanks.
