On Mon, Mar 25, 2024 at 5:54 PM Oscar Benjamin <oscar.j.benjamin@gmail.com> wrote:
On Sat, 9 Mar 2024 at 10:16, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Sat, Mar 9, 2024 at 2:03 AM Oscar Benjamin <
oscar.j.benjamin@gmail.com> wrote:
On Sat, 9 Mar 2024 at 00:44, Charles R Harris <
charlesr.harris@gmail.com> wrote:
About a month from now.
What will happen about a month from now? It might seem obvious to you but I can interpret this in different ways.
To be clear numpy 2.0 is expected to be released in full to the public in about one month's time from today?
Let me give the optimistic and pessimistic timelines. Optimistic:
- 2.0.0b1 later today - 2.0.0rc1 (ABI stable) in 7-10 days - 2.0.0 final release in 1 month
Pessimistic:
- 2.0.0b1 within a few days - 2.0.0rc1 (ABI stable) in 2 weeks - 2.0.0rc2 in 4 weeks - 2.0.0rc3 in 6 weeks - 2.0.0 final release in 8 weeks
Thanks Ralf and Chuck. Sorry, I meant to reply to this earlier but got distracted with other things.
We are now 16 days into the future so NumPy 2.0 would be 2 weeks time for the optimistic timescale.
I assume that now the beta release is out the intention is no further breaking changes. Then if SymPy master is currently compatible with NumPy 2.0.0b1 a good time for a SymPy release with accumulated fixes is... ASAP!
Presumably now that NumPy 2.0 is branched downstream projects should test in CI against the prereleases (pip install --pre numpy) rather than the nightly wheels. (SymPy does not usually test against the nightly wheels. I added that for NumPy 2.0 but maybe we should keep it...)
The rc1 release is now waiting on pybind11, so there is an (uncertain) delay. Chuck