[Numpy-discussion] Re: numpy 2.0.x has been branched.
On Sat, Mar 9, 2024 at 2:03 AM Oscar Benjamin wrote: > 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? > 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 For projects which have nontrivial usage of the NumPy API (and especially if they also use the C API), I'd recommend: 1. Check whether things work with 2.0.0b1, ideally asap so if there is anything we missed we can catch it before rc1. Perhaps do a pre-release of your own package 2. Do a final release after 2.0.0rc1 - ideally as soon as possible after, and definitely before the final 2.0.0 release For (2), note that there are a ton of packages that do not have correct upper bounds, so if you haven't done your own new release that is compatible with both 2.0.0 and 1.26.x *before* 2.0.0 comes out, the users of your project are likely to have a hard time. Cheers, Ralf ___ 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.
Maybe someone composes another preemptive blog post about this? I think this needs some banging on the pans to soften its landing since NumPy 2.0 is a big deal. The community will take care of its circulation in typical places. We always get the grilling no matter the outcome :) But I think it is important that at least package maintainers see this and react to it. On Sat, Mar 9, 2024 at 11:12 AM Ralf Gommers wrote: > > > On Sat, Mar 9, 2024 at 2:03 AM Oscar Benjamin > wrote: > >> 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? >> > > 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 > > For projects which have nontrivial usage of the NumPy API (and especially > if they also use the C API), I'd recommend: > 1. Check whether things work with 2.0.0b1, ideally asap so if there is > anything we missed we can catch it before rc1. Perhaps do a pre-release of > your own package > 2. Do a final release after 2.0.0rc1 - ideally as soon as possible after, > and definitely before the final 2.0.0 release > > For (2), note that there are a ton of packages that do not have correct > upper bounds, so if you haven't done your own new release that is > compatible with both 2.0.0 and 1.26.x *before* 2.0.0 comes out, the users > of your project are likely to have a hard time. > > Cheers, > Ralf > > ___ > 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: ilhanpo...@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] Automatic Clipping of array to upper / lower bounds of dtype
Hello, Can't find answer to this anywhere. What I would like is to automatically clip the values if they breach the bounds. I have done a simple clipping, and overwritten __iadd__, __isub__, __setitem__, … But I am wandering if there is a specified way to do this. Or maybe at least a centralised place exists to do such thing? E.g. Only 1 method to override? Regards and thanks, dgpb ___ 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
