<div dir="ltr">Hi Peter, <div><br></div><div>I do not think that would be a problem. From my (limited) understanding any 3.4 code would still be compatible with any version higher just not the other way around. </div><div><br></div><div>Thanks</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 18, 2018 at 10:50 AM Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Biopythoneers,<br>
<br>
I would like to drop Python 3.4 support in order to reduce<br>
our continuous integration testing requirements.<br>
<br>
We currently (as of Biopython 1.73) support Python 2.7<br>
(until 2020), and Python 3.4, 3.5, 3.6, 3.7.<br>
<br>
According to the Python website, Python 3.4 and 3.5 are<br>
still getting security fixes, with the final release of Python 3.4<br>
expected March 2019 in line with end-of-life 2019-03-16.<br>
<br>
<a href="https://www.python.org/dev/peps/pep-0429/" rel="noreferrer" target="_blank">https://www.python.org/dev/peps/pep-0429/</a><br>
<a href="https://devguide.python.org/#status-of-python-branches" rel="noreferrer" target="_blank">https://devguide.python.org/#status-of-python-branches</a><br>
<br>
Would dropping Python 3.4 support inconvenience any<br>
Biopython users? Should we wait one more release<br>
(i.e. Biopython 1.74, which we might aim to release in<br>
March 2019?)<br>
<br>
Thanks,<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="http://mailman.open-bio.org/mailman/listinfo/biopython" rel="noreferrer" target="_blank">http://mailman.open-bio.org/mailman/listinfo/biopython</a><br>
</blockquote></div>