Hi all, a small piece of information:
NumPy 1.x was not released with support for Python 3.14. Most of the time, a too new Python versions (in recent past) just broke compilation. However, this time around optimization work together with the one bit of arcane optimization tricks in NumPy *will* cause silently incorrect results in most non-trivial code [1]. There are no releases to yank or upper bounds to set so I didn't think we can actually do anything about it. But this just came up again (this time in pandas). IThe only (new) idea I have would be to upload a Python 1.26 + Python 3.14 wheel that includes no code besides raising an error at install time. (Anyone who is running into issues is compiling NumPy from scratch, but I guess they would probably use the wheel first if available.) Cheers, Sebastian [1] May affect windows builds less badly, where NumPy doesn't do this trick, but what does it matter.... _______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/numpy-discussion.python.org Member address: [email protected]
