Re: Planning to drop Python 2 support by 2020?

--===============6889474739943253753==
Content-Type: multipart/alternative; boundary="001a113e4180e628e10552a5a809"

--001a113e4180e628e10552a5a809
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I understand that some folks (surely not only Joao) have old code, but to
be quite frank, supporting old code is shifting the burden to us by
something we have no real fault. It is not our responsibility if people did
not take appropriate decisions over time. Should we be supporting Python 1?

Other than a burden on us, it is also a burden on users that did the
recommended thing (remember this comes from CPython - not us) because
Biopython could be using more modern features and it is not.

Also, being quite cynical, I think the project would profit more to be
modern than supporting very old stuff. Biopython shows its age. Compared to
any other big Python project out there that I can think off. it is clearly
behind the curve.

Come 2020, old Biopython versions will always be available, people should
use those if they need Python 2 support.

On 22 June 2017 at 05:00, Peter Cock <[email protected]> wrote:

> Thank Joao,
>
> I am interpreting the pledge as dropping any expectation of support
> for Biopython on Python 2 after 2020, but with enough leeway for an
> emergency fix release if required after thereafter.
>
> (Much like how Microsoft officially ended Windows XP support some
> time ago, but does occasionally release critical security fixes)
>
> Peter
>
> On Thu, Jun 22, 2017 at 11:49 AM, Jo=C3=A3o Rodrigues
> <[email protected]> wrote:
> > Hi Peter,
> >
> > I believe we are on the same page, I just think it's important to menti=
on
> > these issues explicitly in writing somewhere because they *will* pop up=
.
> The
> > pledge should highlight that it drops support for developing for Python
> 2.x,
> > and this I completely agree with. However, I am firmly against dropping
> all
> > support for users stuck with Python 2.x. It's a matter of wording and
> > interpretation of the pledge text I guess..
> >
> > So yes, I agree.
> >
> > Cheers,
> >
> > Jo=C3=A3o
>
> _______________________________________________
> Biopython-dev mailing list
> [email protected]
> http://mailman.open-bio.org/mailman/listinfo/biopython-dev
>



--=20
Tiago Antao
Scientific and HPC programmer
http://tiago.org
https://github.com/tiagoantao/

--001a113e4180e628e10552a5a809
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I understand that some folks (surel=
y not only Joao) have old code, but to be quite frank, supporting old code =
is shifting the burden to us by something we have no real fault. It is not =
our responsibility if people did not take appropriate decisions over time. =
Should we be supporting Python 1?</div><div><br></div><div>Other than a bur=
den on us, it is also a burden on users that did the recommended thing (rem=
ember this comes from CPython - not us) because Biopython could be using mo=
re modern features and it is not.</div><div><br></div><div>Also, being quit=
e cynical, I think the project would profit more to be modern than supporti=
ng very old stuff. Biopython shows its age. Compared to any other big Pytho=
n project out there that I can think off. it is clearly behind the curve.</=
div><div><br></div><div>Come 2020, old Biopython versions will always be av=
ailable, people should use those if they need Python 2 support.</div></div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 22 June 2017 a=
t 05:00, Peter Cock <span dir=3D"ltr">&lt;<a href=3D"mailto:p.j.a.cock@goog=
lemail.com" target=3D"_blank">[email protected]</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Thank Joao,<br>
<br>
I am interpreting the pledge as dropping any expectation of support<br>
for Biopython on Python 2 after 2020, but with enough leeway for an<br>
emergency fix release if required after thereafter.<br>
<br>
(Much like how Microsoft officially ended Windows XP support some<br>
time ago, but does occasionally release critical security fixes)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Peter<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On Thu, Jun 22, 2017 at 11:49 AM, Jo=C3=A3o Rodrigues<br>
&lt;<a href=3D"mailto:[email protected]">j.p.g.l.m.rodrigues@gm=
ail.com</a><wbr>&gt; wrote:<br>
&gt; Hi Peter,<br>
&gt;<br>
&gt; I believe we are on the same page, I just think it&#39;s important to =
mention<br>
&gt; these issues explicitly in writing somewhere because they *will* pop u=
p. The<br>
&gt; pledge should highlight that it drops support for developing for Pytho=
n 2.x,<br>
&gt; and this I completely agree with. However, I am firmly against droppin=
g all<br>
&gt; support for users stuck with Python 2.x. It&#39;s a matter of wording =
and<br>
&gt; interpretation of the pledge text I guess..<br>
&gt;<br>
&gt; So yes, I agree.<br>
&gt;<br>
&gt; Cheers,<br>
&gt;<br>
&gt; Jo=C3=A3o<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">_______________________=
_______<wbr>_________________<br>
Biopython-dev mailing list<br>
<a href=3D"mailto:[email protected]">Biopython-dev@mailman=
.open-<wbr>bio.org</a><br>
<a href=3D"http://mailman.open-bio.org/mailman/listinfo/biopython-dev" rel=
=3D"noreferrer" target=3D"_blank">http://mailman.open-bio.org/<wbr>mailman/=
listinfo/biopython-dev</a></div></div></blockquote></div><br><br clear=3D"a=
ll"><div><br></div>-- <br><div class=3D"gmail_signature" data-smartmail=3D"=
gmail_signature"><div dir=3D"ltr">Tiago Antao<div>Scientific and HPC progra=
mmer</div><div><a href=3D"http://tiago.org" target=3D"_blank">http://tiago.=
org</a></div><div><a href=3D"https://github.com/tiagoantao/" target=3D"_bla=
nk">https://github.com/tiagoantao/</a><br></div></div></div>
</div>

--001a113e4180e628e10552a5a809--

--===============6889474739943253753==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Biopython-dev mailing list
[email protected]
http://mailman.open-bio.org/mailman/listinfo/biopython-dev
--===============6889474739943253753==--