<div><div dir="auto">A brief discussion with Chris about next steps in 2020 once this release is done.</div></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">Chris Rands</strong> <span dir="auto"><<a href="mailto:c_rands100@hotmail.com">c_rands100@hotmail.com</a>></span><br>Date: Wed, 18 Dec 2019 at 18:03<br>Subject: Re: [Biopython] Biopython 1.76 plans<br>To: Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>><br></div><br><br>
<div dir="ltr">
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Thanks Peter, I like your plan, and please do fwd to the mailing list if you think it's of broad interest</div></div><div dir="ltr">
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Chris</div>
<div>
<div id="m_-8818268983265693262appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<hr style="display:inline-block;width:98%">
<div id="m_-8818268983265693262divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com" target="_blank">p.j.a.cock@googlemail.com</a>><br>
<b>Sent:</b> 18 December 2019 6:09 PM<br>
<b>To:</b> Chris Rands <<a href="mailto:c_rands100@hotmail.com" target="_blank">c_rands100@hotmail.com</a>><br>
<b>Subject:</b> Re: [Biopython] Biopython 1.76 plans</font>
<div> </div>
</div>
<div><font size="2"><span style="font-size:11pt">
<div>Shall we stay on the list? My plan:<br>
<br>
(1) Release Biopython 1.76 with Python 2.7 and 3.5 support<br>
(2) Turn off testing under Python 2.7 and 3.5<br>
<br>
Then tackle the low handing fruit (in no particular order):<br>
<br>
(3) Remove Bio._py3k compatibility shim<br>
(4) Look for and remove other Python 2 specific workarounds<br>
(5) Remove no longer needed __future__ imports etc<br>
(6) Remove all the Python 2/3 overhead in the C code<br>
<br>
Also, where sensible and after appropriate discussion, take<br>
advantage of new language or standard library features in<br>
Python 3.6+ as appropriate (e.g. sorted dictionaries by default<br>
without needing to import OrderedDict from collections).<br>
<br>
I hadn't thought much about f-strings (beyond that I'm not<br>
used to them and that makes me dislike them), but that could<br>
be a good example.<br>
<br>
Peter<br>
<br>
On Wed, Dec 18, 2019 at 4:52 PM Chris Rands <<a href="mailto:c_rands100@hotmail.com" target="_blank">c_rands100@hotmail.com</a>> wrote:<br>
><br>
> Dear Peter,<br>
><br>
> Apologies if this has already been discussed, but is the plan to merely passively drop support for Python 2/Python 3.5 or to also actively update existing code?<br>
><br>
> For example, in 2020, would you merge a PR converting all string formatting to f-strings (supported since Python 3.6) or removing all `from __future__ import print_function` lines?<br>
><br>
> Best, Chris<br>
><br>
><br>
> ________________________________<br>
> From: Biopython <biopython-bounces+c_rands100=<a href="mailto:hotmail.com@mailman.open-bio.org" target="_blank">hotmail.com@mailman.open-bio.org</a>> on behalf of Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com" target="_blank">p.j.a.cock@googlemail.com</a>><br>
> Sent: 18 December 2019 5:16 PM<br>
> To: Biopython Mailing List <<a href="mailto:biopython@mailman.open-bio.org" target="_blank">biopython@mailman.open-bio.org</a>><br>
> Subject: [Biopython] Biopython 1.76 plans<br>
><br>
> Dear Biopythoneers,<br>
><br>
> As has been discussed earlier, we hope to release Biopython 1.76 this<br>
> month (December 2019). This will be a significant milestone as our<br>
> final release to support Python 2 which is now officially at end of<br>
> life:<br>
><br>
> <a href="https://mailman.open-bio.org/pipermail/biopython/2019-November/016735.html" target="_blank">
https://mailman.open-bio.org/pipermail/biopython/2019-November/016735.html</a><br>
><br>
> <a href="https://python3statement.org/" target="_blank">https://python3statement.org/</a><br>
><br>
> Additionally, I am proposing this also be the final release to support<br>
> Python 3.5:<br>
><br>
> <a href="https://mailman.open-bio.org/pipermail/biopython/2019-December/016737.html" target="_blank">
https://mailman.open-bio.org/pipermail/biopython/2019-December/016737.html</a><br>
><br>
> We had a couple of issues reported with Biopython 1.75 post release,<br>
> mainly from the Debian packaging team covering C code doctests and C<br>
> code on alternative CPUs - which are now being tested via TravisCI.<br>
><br>
> Otherwise I am not aware of any reported issues which would be a<br>
> release blocker.<br>
><br>
> If no one has any objections, I propose to do the release this Friday,<br>
> 20 December 2019.<br>
><br>
> Any thoughts?<br>
><br>
> Thank you,<br>
><br>
> Peter<br>
> _______________________________________________<br>
> Biopython mailing list - <a href="mailto:Biopython@mailman.open-bio.org" target="_blank">Biopython@mailman.open-bio.org</a><br>
> <a href="https://mailman.open-bio.org/mailman/listinfo/biopython" target="_blank">https://mailman.open-bio.org/mailman/listinfo/biopython</a><br>
</div>
</span></font></div>
</div>
</div>
</div></div>