[Biopython] Biopython 1.84: [numpy/numpy] NumPy 2.0 development status & announcements (Issue #24300)

--===============6443549470640432968==
Content-Type: multipart/alternative; boundary="000000000000419591061339fc2c"

--000000000000419591061339fc2c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

FYI, this looks like a good reason to be ready for another Biopython
release in a couple of weeks time. I can=E2=80=99t currently think of any b=
locking
issues=E2=80=A6

Peter

---------- Forwarded message ---------
From: Ralf Gommers <[email protected]>
Date: Sat, 9 Mar 2024 at 10:13
Subject: Re: [numpy/numpy] NumPy 2.0 development status & announcements
(Issue #24300)
To: numpy/numpy <[email protected]>
Cc: Peter Cock <[email protected]>, Manual <
[email protected]>


The maintenance/2.0.x 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:

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.

=E2=80=94
Reply to this email directly, view it on GitHub
<https://github.com/numpy/numpy/issues/24300#issuecomment-1986815755>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPTVYHHHF43USCKKKM26LY=
XLODVAVCNFSM6AAAAAA26CUHM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWHAY=
TKNZVGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: <numpy/numpy/issues/24300/[email protected]>

--000000000000419591061339fc2c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">FYI, this looks like a good reason to be ready for anothe=
r Biopython release in a couple of weeks time. I can=E2=80=99t currently th=
ink of any blocking issues=E2=80=A6</div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">Peter</div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">---------- Forwarded message ---------<br>From: <stro=
ng class=3D"gmail_sendername" dir=3D"auto">Ralf Gommers</strong> <span dir=
=3D"auto">&lt;<a href=3D"mailto:[email protected]">notifications@git=
hub.com</a>&gt;</span><br>Date: Sat, 9 Mar 2024 at 10:13<br>Subject: Re: [n=
umpy/numpy] NumPy 2.0 development status &amp; announcements (Issue #24300)=
<br>To: numpy/numpy &lt;<a href=3D"mailto:[email protected]">numpy@n=
oreply.github.com</a>&gt;<br>Cc: Peter Cock &lt;<a href=3D"mailto:p.j.a.coc=
[email protected]">[email protected]</a>&gt;, Manual &lt;<a href=3D"=
mailto:[email protected]">[email protected]</a>&gt;<br></di=
v><br><br><p></p>
<p dir=3D"auto">The <code class=3D"notranslate" style=3D"font-family:monosp=
ace">maintenance/2.0.x</code> branch has been created, so we&#39;re almost =
there - beta 1 will arrive without hours to days. I&#39;ll re-post from the=
 mailing list:</p>
<p dir=3D"auto">Let me give the optimistic and pessimistic timelines. Optim=
istic:</p>
<ul dir=3D"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=3D"auto">Pessimistic:</p>
<ul dir=3D"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=3D"auto">For projects which have nontrivial usage of the NumPy API (=
and especially if they also use the C API), I&#39;d recommend:</p>
<ol dir=3D"auto">
<li>Check whether things work with 2.0.0b1, ideally asap so if there is any=
thing we missed we can catch it before rc1. Perhaps do a pre-release of you=
r 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=3D"auto">For (2), note that there are a ton of packages that do not =
have correct upper bounds, so if you haven&#39;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 o=
ut, the users of your project are likely to have a hard time.</p>

<p style=3D"font-size:small;color:rgb(102,102,102)">=E2=80=94<br>Reply to t=
his email directly, <a href=3D"https://github.com/numpy/numpy/issues/24300#=
issuecomment-1986815755" target=3D"_blank">view it on GitHub</a>, or <a hre=
f=3D"https://github.com/notifications/unsubscribe-auth/AAAPTVYHHHF43USCKKKM=
26LYXLODVAVCNFSM6AAAAAA26CUHM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOB=
WHAYTKNZVGU" target=3D"_blank">unsubscribe</a>.<br>You are receiving this b=
ecause you are subscribed to this thread.<img src=3D"https://github.com/not=
ifications/beacon/AAAPTVZQ53SXWGFMLVX6ZN3YXLODVA5CNFSM6AAAAAA26CUHM6WGG33NN=
VSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTWNRTQW.gif" height=3D=
"1" width=3D"1" alt=3D""><span style=3D"font-size:0px;display:none;overflow=
:hidden;opacity:0;width:0px;height:0px;max-width:0px;max-height:0px;color:t=
ransparent">Message ID: <span>&lt;numpy/numpy/issues/24300/1986815755</span=
><span>@</span><span>github</span><span>.</span><span>com&gt;</span></span>=
</p>
</div></div>

--000000000000419591061339fc2c--

--===============6443549470640432968==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Biopython mailing list  -  [email protected]
https://mailman.open-bio.org/mailman/listinfo/biopython

--===============6443549470640432968==--