How bad are the NumPy 2.0 breakages in SymPy? We could do a backport release if they are serious.
Aaron Meurer On Fri, Mar 8, 2024 at 2:46 PM Oscar Benjamin <[email protected]> wrote: > > Hi Chuck, > > Is there a rough expected landing time for NumPy 2.0? > > Also does the branching mean that the intention/guarantee is not to > make further incompatible changes? > > SymPy's current master branch is compatible with the current NumPy > master branch but SymPy's last release is not and will not be > compatible with NumPy 2.0. That means that we want to have a SymPy > release before NumPy 2.0 that includes the changes needed in > preparation. Ideally I also want that SymPy release to be made after > NumPy has finished making breaking changes though. > > Basically I want to know what the interval of time is between NumPy > finishing its incompatible changes and NumPy 2.0 actually being > released (to the extent that that is knowable). > > Oscar > > On Fri, 8 Mar 2024 at 21:23, Charles R Harris <[email protected]> > wrote: > > > > Hi All, > > > > Numpy 2.0.x has been branched, further work on the release notes should be > > made against that branch. The main branch is now 2.1.0. > > > > Chuck > > _______________________________________________ > > 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] > _______________________________________________ > 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] _______________________________________________ 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]
