[Numpy-discussion] numpy 2.0.x has been branched.
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 -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: numpy 2.0.x has been branched.
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 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 -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: oscar.j.benja...@gmail.com ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: numpy 2.0.x has been branched.
On Fri, Mar 8, 2024 at 2:48 PM Oscar Benjamin 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 > > We plan on a beta release, which will probably have a stable API, but not guaranteed, then an rc1. At that point the API should be stable and the final release will wait for the most important downstream projects to make compatible releases. I would hope we are talking about a month in total, but it will depend on how things go. Chuck ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: numpy 2.0.x has been branched.
On Fri, 8 Mar 2024 at 22:27, Charles R Harris wrote: > > We plan on a beta release, which will probably have a stable API, but not > guaranteed, then an rc1. At that point the API should be stable and the final > release will wait for the most important downstream projects to make > compatible releases. I would hope we are talking about a month in total, but > it will depend on how things go. I can understand if it is difficult to answer this but I just want a best estimate answer: You say that it is a month in total but when is the start and end of that month? Are we talking next week or 3 months from now or something else? -- Oscar ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: numpy 2.0.x has been branched.
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 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 > 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 -- numpy-discussion@python.org > > To unsubscribe send an email to numpy-discussion-le...@python.org > > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > > Member address: oscar.j.benja...@gmail.com > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: asmeu...@gmail.com ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: numpy 2.0.x has been branched.
On Fri, 8 Mar 2024 at 23:31, Aaron Meurer wrote: > > How bad are the NumPy 2.0 breakages in SymPy? We could do a backport > release if they are serious. I don't remember exactly what needed changing but some basic things in sympy needed changing because of basic changes in numpy. I don't see what purpose a backport release would serve. I would like to get out a sympy release right now. I would also like to know when is the right time to put out a release that is tested with all new numpy changes and that should be expected to be compatible with numpy 2.0. I am asking for a timeline: is numpy 2.0 coming out in 1 week, 1 month, 2 months, 3 months, 6 months, 12 months? I understand if it is difficult to be precise but right now I have no idea what timeline anyone is talking about and I am pretty sure that numpy folks have a much clearer idea: please share it with me! -- Oscar ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: numpy 2.0.x has been branched.
On Fri, Mar 8, 2024 at 4:45 PM Oscar Benjamin wrote: > On Fri, 8 Mar 2024 at 23:31, Aaron Meurer wrote: > > > > How bad are the NumPy 2.0 breakages in SymPy? We could do a backport > > release if they are serious. > > I don't remember exactly what needed changing but some basic things in > sympy needed changing because of basic changes in numpy. > > I don't see what purpose a backport release would serve. I would like > to get out a sympy release right now. I would also like to know when > is the right time to put out a release that is tested with all new > numpy changes and that should be expected to be compatible with numpy > 2.0. > > I am asking for a timeline: is numpy 2.0 coming out in 1 week, 1 > month, 2 months, 3 months, 6 months, 12 months? > > I understand if it is difficult to be precise but right now I have no > idea what timeline anyone is talking about and I am pretty sure that > numpy folks have a much clearer idea: please share it with me! > > About a month from now. Chuck ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: numpy 2.0.x has been branched.
On Sat, 9 Mar 2024 at 00:44, Charles R Harris 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? -- Oscar ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
