Re: [Biopython] Planning Biopython 1.85

--===============2854370571596141126==
Content-Type: multipart/alternative; boundary="0000000000007f0cb306224e6ace"

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

Also, I think Biopython 1.85 should be our last release to support Python
3.9 (which we declared deprecated in Biopython 1.84).

One of the small cosmetic advantages of moving to Python 3.10 onward is
more concise type annotation notation, but I'm sure you all have your own
favorite new features.

Peter

On Mon, Sep 9, 2024 at 12:55=E2=80=AFPM Peter Cock <[email protected]=
om>
wrote:

> Dear Biopythoneers,
>
> We released Biopython 1.84 at the end of June, so three months later whic=
h
> was our typical cadence in the past would put us due for another release =
at
> the end of this month.
>
> There are practical reasons to do this too -
> https://peps.python.org/pep-0719/ - Python 3.13 is being released at the
> start of October, and there is a minor compilation problem with some of o=
ur
> legacy C code (since addressed) which complicates releasing a Biopython
> 1.84 wheel for Python 3.13. We can in principle release a Python 3.13
> compatible release now (compiled against the release candidates ahead of
> the formal release at the start of October).
>
> However, as unfortunately has become common, we have a backlog of open
> issues and open pull requests. Please speak up with any key issues or
> overlooked pull requests you think need to be addressed for Biopython 1.8=
5,
> and if you can help review or tests them, even better!
>
> I'd be happy to help a volunteer do the release itself, although I see no=
w
> that I didn't finish updating
> https://biopython.org/wiki/Building_a_release alongside doing Biopython
> 1.84 which changed the way the documentation is built and published. By
> default, I'll do the Biopython 1.85 release and get that how-to updated.
>
> Thank you all,
>
> Peter
>
>

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

<div dir=3D"ltr"><div>Also, I think Biopython 1.85 should be our last relea=
se to support Python 3.9 (which we declared deprecated in Biopython 1.84).<=
/div><div><br></div><div>One of the small cosmetic advantages of moving to =
Python 3.10 onward is more concise type annotation notation, but I&#39;m su=
re you all have your own favorite new features.<br></div><div><br></div><di=
v>Peter<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Mon, Sep 9, 2024 at 12:55=E2=80=AFPM Peter Cock &lt;<a =
href=3D"mailto:[email protected]">[email protected]</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div>Dear Biopythoneers,</div><div><br></div><div>We released Biop=
ython 1.84 at the end of June, so three months later which was our typical =
cadence in the past would put us due for another release at the end of this=
 month.</div><div><br></div><div>There are practical reasons to do this too=
 - <a href=3D"https://peps.python.org/pep-0719/" target=3D"_blank">https://=
peps.python.org/pep-0719/</a> - Python 3.13 is being released at the start =
of October, and there is a minor compilation problem with some of our legac=
y C code (since addressed) which complicates releasing a Biopython 1.84 whe=
el for Python 3.13. We can in principle release a Python 3.13 compatible re=
lease now (compiled against the release candidates ahead of the formal rele=
ase at the start of October).</div><div><br></div><div>However, as unfortun=
ately has become common, we have a backlog of open issues and open pull req=
uests. Please speak up with any key issues or overlooked pull requests you =
think need to be addressed for Biopython 1.85, and if you can help review o=
r tests them, even better!</div><div><br></div><div>I&#39;d be happy to hel=
p a volunteer do the release itself, although I see now that I didn&#39;t f=
inish updating <a href=3D"https://biopython.org/wiki/Building_a_release" ta=
rget=3D"_blank">https://biopython.org/wiki/Building_a_release</a> alongside=
 doing Biopython 1.84 which changed the way the documentation is built and =
published. By default, I&#39;ll do the Biopython 1.85 release and get that =
how-to updated.<br></div><div><br></div><div>Thank you all,</div><div><br><=
/div><div>Peter</div><div><br></div></div>
</blockquote></div>

--0000000000007f0cb306224e6ace--

--===============2854370571596141126==
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

--===============2854370571596141126==--