<div dir="auto">FYI, this looks like a good reason to be ready for another Biopython release in a couple of weeks time. I can’t currently think of any blocking issues…</div><div dir="auto"><br></div><div dir="auto">Peter</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Ralf Gommers</strong> <span dir="auto"><<a href="mailto:notifications@github.com">notifications@github.com</a>></span><br>Date: Sat, 9 Mar 2024 at 10:13<br>Subject: Re: [numpy/numpy] NumPy 2.0 development status & announcements (Issue #24300)<br>To: numpy/numpy <<a href="mailto:numpy@noreply.github.com">numpy@noreply.github.com</a>><br>Cc: Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>>, Manual <<a href="mailto:manual@noreply.github.com">manual@noreply.github.com</a>><br></div><br><br><p></p>
<p dir="auto">The <code class="notranslate" style="font-family:monospace">maintenance/2.0.x</code> branch has been created, so we're almost there - beta 1 will arrive without hours to days. I'll re-post from the mailing list:</p>
<p dir="auto">Let me give the optimistic and pessimistic timelines. Optimistic:</p>
<ul dir="auto">
<li>2.0.0b1 later today</li>
<li>2.0.0rc1 (ABI stable) in 7-10 days</li>
<li>2.0.0 final release in 1 month</li>
</ul>
<p dir="auto">Pessimistic:</p>
<ul dir="auto">
<li>2.0.0b1 within a few days</li>
<li>2.0.0rc1 (ABI stable) in 2 weeks</li>
<li>2.0.0rc2 in 4 weeks</li>
<li>2.0.0rc3 in 6 weeks</li>
<li>2.0.0 final release in 8 weeks</li>
</ul>
<p dir="auto">For projects which have nontrivial usage of the NumPy API (and especially if they also use the C API), I'd recommend:</p>
<ol dir="auto">
<li>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</li>
<li>Do a final release after 2.0.0rc1 - ideally as soon as possible after, and definitely before the final 2.0.0 release</li>
</ol>
<p dir="auto">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 <em>before</em> 2.0.0 comes out, the users of your project are likely to have a hard time.</p>
<p style="font-size:small;color:rgb(102,102,102)">—<br>Reply to this email directly, <a href="https://github.com/numpy/numpy/issues/24300#issuecomment-1986815755" target="_blank">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAAPTVYHHHF43USCKKKM26LYXLODVAVCNFSM6AAAAAA26CUHM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWHAYTKNZVGU" target="_blank">unsubscribe</a>.<br>You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAAPTVZQ53SXWGFMLVX6ZN3YXLODVA5CNFSM6AAAAAA26CUHM6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTWNRTQW.gif" height="1" width="1" alt=""><span style="font-size:0px;display:none;overflow:hidden;opacity:0;width:0px;height:0px;max-width:0px;max-height:0px;color:transparent">Message ID: <span><numpy/numpy/issues/24300/1986815755</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
</div></div>