<html><head></head><body><div class="ydpdde5a573yahoo-style-wrap" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 10px;"><div></div>
<div dir="ltr" data-setdir="false">>To start the conversation going, I would like to suggest we drop Python 3.5<br><div><div dir="ltr">support at the same time that we drop Python 2.7 (after our first release in<br></div><div dir="ltr">2020).<br></div><div dir="ltr"><br></div><div dir="ltr" data-setdir="false">Let's drop Python 2.7 already in our first release in 2020, so that all releases from 2020 are Python3 only.</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><div><br></div></div><div><br></div>
</div><div id="yahoo_quoted_4115603263" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, November 18, 2019, 10:33:55 PM GMT+9, Peter Cock <p.j.a.cock@googlemail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Dear Biopythoneers,<br></div><div dir="ltr"><br></div><div dir="ltr">We have already announced that we are dropping Python 2.7 support in<br></div><div dir="ltr">early 2020, which will leave us supporting Python 3.5, 3.6, 3.7 and 3.8.<br></div><div dir="ltr"><br></div><div dir="ltr">Both Python 3.5 and 3.6 are no longer getting bug fixes, only security<br></div><div dir="ltr">fixes though to September 2020 and December 2021 respectively<br></div><div dir="ltr">(based on a five year life cycle):<br></div><div dir="ltr"><br></div><div dir="ltr"><a href="https://devguide.python.org/#status-of-python-branches" target="_blank">https://devguide.python.org/#status-of-python-branches</a><br></div><div dir="ltr"><br></div><div dir="ltr">As usual, the motivation is both reducing the number of combinations we<br></div><div dir="ltr">must test on, and being able to take advantage of language improvements.<br></div><div dir="ltr">In this case we would be able to assume sorted dictionaries (a language<br></div><div dir="ltr">feature guaranteed in Python 3.7 onwards, but actually implemented in<br></div><div dir="ltr">C Python 3.6 and PyPy so effectively available in Python 3.6 onwards).<br></div><div dir="ltr"><br></div><div dir="ltr">In similar past discussion the only real obstacle to dropping support for<br></div><div dir="ltr">older Python versions has been when a widely used Linux system had<br></div><div dir="ltr">it as the default system Python - although nowadays with conda etc it<br></div><div dir="ltr">is very easy to ignore that in favour of a user-specific Python setup.<br></div><div dir="ltr"><br></div><div dir="ltr">Are any of our mailing list subscribers still using Python 3.5? If so,<br></div><div dir="ltr">would having to update be a major hurdle?<br></div><div dir="ltr"><br></div><div dir="ltr">To start the conversation going, I would like to suggest we drop Python 3.5<br></div><div dir="ltr">support at the same time that we drop Python 2.7 (after our first release in<br></div><div dir="ltr">2020).<br></div><div dir="ltr"><br></div><div dir="ltr">Peter<br></div><div dir="ltr">_______________________________________________<br></div><div dir="ltr">Biopython mailing list - <a ymailto="mailto:Biopython@mailman.open-bio.org" href="mailto:Biopython@mailman.open-bio.org">Biopython@mailman.open-bio.org</a><br></div><div dir="ltr"><a href="https://mailman.open-bio.org/mailman/listinfo/biopython" target="_blank">https://mailman.open-bio.org/mailman/listinfo/biopython</a><br></div></div>
</div>
</div></body></html>