<html><head></head><body><div class="ydp78766a5dyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:10px;"><div></div>
<div dir="ltr" data-setdir="false">Hi Peter,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I am fine with that, but in practice there are cases where dedicated code is needed in Biopython to support python2, and especially for Python/C interfacing this can be quite painful (in particular for strings, e.g. Seq objects, and for arrays). As it doesn't make sense to spend the time to write such code now but to remove it in six months after we drop python2 support, personally I would develop for python3 only now, but hold off on making the pull request until after January 1st.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Best,</div><div dir="ltr" data-setdir="false">-Michiel<br></div><div><br></div>
</div><div id="yahoo_quoted_3398084737" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, July 15, 2019, 6:38:33 AM GMT+9, Peter Cock <p.j.a.cock@googlemail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi Michiel,<br clear="none"><br clear="none">As I understand it, Python 2.7 is supported until Jan 2020:<br clear="none"><br clear="none"><a shape="rect" href="https://python3statement.org/" target="_blank">https://python3statement.org/</a><br clear="none"><br clear="none">So, I am hoping the first release in 2020 will be out final release<br clear="none">to include Python 2.7 support - after which in line with our past<br clear="none">statement's we can drop support for Python 2. We seem to be in<br clear="none">agreement on this? Shall we make the README language on<br clear="none">this firmer?<br clear="none"><br clear="none">Separately, I'd really like to get back to more frequent releases -<br clear="none">automating the API documentation will help with that (epydoc is<br clear="none">a pain), as would automating the main Tutorial builds (more on<br clear="none">that later). So I would expect/hope to see Biopython 1.75 in the<br clear="none">autumn/fall, and then Biopython 1.76 around Jan 2020 being<br clear="none">the final release supporting Python 2.7?<br clear="none"><br clear="none">Peter<br clear="none"><div class="yqt3012646777" id="yqtfd53044"><br clear="none">On Sun, Jul 14, 2019 at 10:51 AM Michiel de Hoon <<a shape="rect" ymailto="mailto:mjldehoon@yahoo.com" href="mailto:mjldehoon@yahoo.com">mjldehoon@yahoo.com</a>> wrote:<br clear="none">><br clear="none">> Hi Peter, everybody,<br clear="none">><br clear="none">> As it's mid-July now, and on average there is approximately six months between Biopython releases, can we assume that the next Biopython release after this one will be in 2020? If so, since we plan to move to python3 from 2020, will 1.74 be the last release that supports python2? Then perhaps we should announce this as part of the release. For developers, we should also clarify if (a) new Biopython code after the 1.74 release should still support python2; and (b) if we should encourage developers to start removing python2 support from Biopython after the 1.74 release. Personally I think that dropping python2 support will reduce the burden on developers, so the sooner the better in my opinion.<br clear="none">><br clear="none">> Best,<br clear="none">> -Michiel<br clear="none">><br clear="none">> On Saturday, July 13, 2019, 3:02:02 AM GMT+9, Peter Cock <<a shape="rect" ymailto="mailto:p.j.a.cock@googlemail.com" href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>> wrote:<br clear="none">><br clear="none">><br clear="none">> Hello all, especially the other developers,<br clear="none">><br clear="none">> We’re again overdue for a Biopython release, especially to have this done before the annual update talk at BOSC later this month.<br clear="none">><br clear="none">> I should be able to do the release Tuesday 16 July, so please hold off merging any major changes for now.<br clear="none">><br clear="none">> My time to review the pull request back log before then will be limited - if there are there any specific issues we can address before then, please comment on GitHub.<br clear="none">><br clear="none">> I would particularly like to merge the new Sphinx API Documentation branch:<br clear="none">><br clear="none">> <a shape="rect" href="https://lists.open-bio.org/pipermail/biopython/2019-July/016632.html" target="_blank">https://lists.open-bio.org/pipermail/biopython/2019-July/016632.html</a><br clear="none">><br clear="none">><br clear="none">> Thank you all,<br clear="none">><br clear="none">> Peter<br clear="none">> _______________________________________________<br clear="none">> Biopython mailing list - <a shape="rect" ymailto="mailto:Biopython@mailman.open-bio.org" href="mailto:Biopython@mailman.open-bio.org">Biopython@mailman.open-bio.org</a><br clear="none">> <a shape="rect" href="https://mailman.open-bio.org/mailman/listinfo/biopython" target="_blank">https://mailman.open-bio.org/mailman/listinfo/biopython</a></div></div></div>
</div>
</div></body></html>