<html><head></head><body><div class="ydp61b3f957yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:10px;"><div></div>
<div dir="ltr" data-setdir="false">If we could make Biopython release 1.76 with python2.7 support before the end of December, then that would be great. Otherwise we could declare Biopython 1.75 to be the last release with Python 2.7 support. In either case, on January 1st we should stop requiring Biopython master to support Python2.7.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I am happy to drop Python3.5 at the same time.<br></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 dir="ltr" data-setdir="false"><br></div><div><br></div>
</div><div id="yahoo_quoted_4980621638" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, November 19, 2019, 12:13:39 AM GMT+9, Peter Cock <p.j.a.cock@googlemail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">If you mean we should aim to release Biopython 1.76 as the final release with<br clear="none">Python 2.7 support in mid/late December 2019 (rather than early January 2020<br clear="none">which is what I was thinking), I wouldn't object.<br clear="none"><br clear="none">Any thoughts on Python 3.5 support?<br clear="none"><br clear="none">Peter<br clear="none"><div class="yqt2171325305" id="yqtfd37698"><br clear="none">On Mon, Nov 18, 2019 at 2:59 PM 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">> >To start the conversation going, I would like to suggest we drop Python 3.5<br clear="none">> support at the same time that we drop Python 2.7 (after our first release in<br clear="none">> 2020).<br clear="none">><br clear="none">> Let's drop Python 2.7 already in our first release in 2020, so that all releases from 2020 are Python3 only.<br clear="none">><br clear="none">> Best,<br clear="none">> -Michiel<br clear="none">><br clear="none">><br clear="none">> On Monday, November 18, 2019, 10:33:55 PM 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">> Dear Biopythoneers,<br clear="none">><br clear="none">> We have already announced that we are dropping Python 2.7 support in<br clear="none">> early 2020, which will leave us supporting Python 3.5, 3.6, 3.7 and 3.8.<br clear="none">><br clear="none">> Both Python 3.5 and 3.6 are no longer getting bug fixes, only security<br clear="none">> fixes though to September 2020 and December 2021 respectively<br clear="none">> (based on a five year life cycle):<br clear="none">><br clear="none">> <a shape="rect" href="https://devguide.python.org/#status-of-python-branches" target="_blank">https://devguide.python.org/#status-of-python-branches</a><br clear="none">><br clear="none">> As usual, the motivation is both reducing the number of combinations we<br clear="none">> must test on, and being able to take advantage of language improvements.<br clear="none">> In this case we would be able to assume sorted dictionaries (a language<br clear="none">> feature guaranteed in Python 3.7 onwards, but actually implemented in<br clear="none">> C Python 3.6 and PyPy so effectively available in Python 3.6 onwards).<br clear="none">><br clear="none">> In similar past discussion the only real obstacle to dropping support for<br clear="none">> older Python versions has been when a widely used Linux system had<br clear="none">> it as the default system Python - although nowadays with conda etc it<br clear="none">> is very easy to ignore that in favour of a user-specific Python setup.<br clear="none">><br clear="none">> Are any of our mailing list subscribers still using Python 3.5? If so,<br clear="none">> would having to update be a major hurdle?<br clear="none">><br clear="none">> To start the conversation going, I would like to suggest we drop Python 3.5<br clear="none">> support at the same time that we drop Python 2.7 (after our first release in<br clear="none">> 2020).<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><br clear="none"></div></div></div>
</div>
</div></body></html>