Re: [Biopython] Planning Biopython 1.85

--===============5329524417465430872==
Content-Type: multipart/alternative; boundary="0000000000003baa9c0621f13ee3"

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

Hi Peter,

I have been using Biopython for several years now and I would like to
contribute to the maintenance of it. I'm not a formally trained programmer
so I'm not sure if I have the needed skills for everything but I'm very
happy to try! My background is a wet bench virologist who learned to code
enough to get his work completed. I'm looking to work on a project that
would allow me to stay practiced and to improve my overall skills.

If you think there could be a place here for me I would love to help.

Cheers,
Sean Brimer

On Mon, Sep 9, 2024 at 6:55=E2=80=AFAM Peter Cock <[email protected]=
m> 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
>
> _______________________________________________
> Biopython mailing list  -  [email protected]
> https://mailman.open-bio.org/mailman/listinfo/biopython
>

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

<div dir=3D"ltr"><div>Hi Peter, <br></div><div><br></div><div>I have been u=
sing Biopython for several years now and I would like to contribute to the =
maintenance of it. I&#39;m not a formally trained programmer so I&#39;m not=
 sure if I have the needed skills for everything but I&#39;m very happy to =
try! My background is a wet bench virologist who learned to code enough to =
get his work completed. I&#39;m looking to work on a project that would all=
ow me to stay practiced and to improve my overall skills.</div><div><br></d=
iv><div>If you think there could be a place here for me I would love to hel=
p. <br></div><div><br></div><div>Cheers, <br></div><div>Sean Brimer<br></di=
v></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">On Mon, Sep 9, 2024 at 6:55=E2=80=AFAM Peter Cock &lt;<a href=3D"mailto:p=
[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>De=
ar Biopythoneers,</div><div><br></div><div>We released Biopython 1.84 at th=
e end of June, so three months later which was our typical cadence in the p=
ast would put us due for another release at the end of this month.</div><di=
v><br></div><div>There are practical reasons to do this too - <a href=3D"ht=
tps://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 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 (compi=
led against the release candidates ahead of the formal release at the start=
 of October).</div><div><br></div><div>However, as unfortunately has become=
 common, we have a backlog of open issues and open pull requests. Please sp=
eak 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 or tests them, ev=
en better!</div><div><br></div><div>I&#39;d be happy to help a volunteer do=
 the release itself, although I see now that I didn&#39;t finish updating <=
a href=3D"https://biopython.org/wiki/Building_a_release" target=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 de=
fault, 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>
_______________________________________________<br>
Biopython mailing list=C2=A0 -=C2=A0 <a href=3D"mailto:Biopython@biopython.=
org" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://mailman.open-bio.org/mailman/listinfo/biopython" rel=3D"=
noreferrer" target=3D"_blank">https://mailman.open-bio.org/mailman/listinfo=
/biopython</a><br>
</blockquote></div>

--0000000000003baa9c0621f13ee3--

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

--===============5329524417465430872==--