On 2025-11-01 20:09, Santiago Vila wrote:
tags 1118038 ftbfs
thanks
Hi. I've checked and the package also FTBFS, with the same error,
so I'm tagging this bug as "ftbfs".
Is it the combination of scipy 1.16 with numpy 2.3 that is triggering
the lmfit-py failure?
Good question. I'm going to use debbisect for that and will tell you
what I find.
Thanks Santiago.
Note: The tracker page says this:
A new upstream version is available: 1.3.4
Would upgrading to such version be an option to address this issue?
BTW: It seems that I did the last three uploads for this package,
but that's more like an accident. In general, I prefer if you or any
of the more experienced team members would care about "upgrade to new
upstream"-type uploads, mainly because I've never done that.
It's possible the new version might help, though I haven't tested it.
For this particular package I won't rush to make uploads myself since
I've previously found upstream to be hostile,
https://github.com/orgs/lmfit/discussions/891
