Re: Planning to drop Python 2 support by 2020?
Peter Cock <[email protected]> Thu, 22 Jun 2017 11:00:14 +0100
| Newsgroups | gmane.comp.python.bio.devel |
|---|---|
| Message-ID | <CAKVJ-_7_vj3wf2uvR0VPsH3yu4+Q+ZHcxHFYjZwZjRMfP9VXYw@mail.gmail.com> |
We now have one Biopython developer not entirely happy about the plan to drop Python 2 support by 2020, João Rodrigues writing on the other thread about ideas for Biopython 2.0: http://mailman.open-bio.org/pipermail/biopython-dev/2017-June/021766.html On 21 June 2017 at 11:44, João Rodrigues <[email protected]> wrote: > > Regarding the pledge, the more I think about it the more conflicted I > feel. On one hand, this will push adoption of Py3.x for the end-user and > allow us to take advantage of new language features. On the other hand, I > still work on clusters with system Py2.6 and with code that chokes with > anything over 2.5. > > ... As I answered there, we have an older cluster and have routinely had to install an extra more recent Python to use in order to run many bioinformatics tools - instead of the system provided elderly system Python. Peter On Thu, Jun 15, 2017 at 11:57 AM, Peter Cock <[email protected]> wrote: > My fellow Biopythoneers, > > I've only seen positive replies, so I propose to add this > commitment to the README.rst file, FAQ in the Tutorial, > and NEWS.rst entry for upcoming biopython 1.70 release. > > Let's say at the start of next week if no one objects? > > We can then ask to have Biopython added to the > http://www.python3statement.org/ site (using the new > logo - yay!). > > We can also include this in the Biopython Project Update > 2017 talk at BOSC next month. > > Regards, > > Peter > > On Sun, Apr 16, 2017 at 10:33 AM, Peter Cock <[email protected]> wrote: >> Correction: NumPy itself is not yet listed on >> http://www.python3statement.org/ but a number >> of related projects like SciPy are. My mistake, sorry. >> >> NumPy are discussing when to drop Python 2.7 >> support on their mailing list right now: >> >> https://mail.python.org/pipermail/numpy-discussion/2017-April/076653.html >> >> I don't think this fundamentally changes the fact we >> should be planning for the end of life for Python 2.7, >> and that 2020 is a sensible target. >> >> Regards, >> >> Peter >> >> On Mon, Dec 5, 2016 at 6:17 PM, Peter Cock <[email protected]> wrote: >>> Dear fellow Biopythoneers, >>> >>> Or next release (Biopython 1.69) drops Python 2.6 support, and will >>> target Python 2.7 and Python 3.3 onwards. >>> >>> While Python 2.7 support will continue in the short to medium term, >>> the Python team themselves currently plan to stop support by 2020. >>> That is only three or four more years, and seems a sensible upper >>> limit for how long Biopython continues to support Python 2.7. >>> >>> Furthermore, NumPy (which a lot of our code depends on) and >>> other high profile relevant projects also intend to drop their >>> Python 2.7 support by 2020 as advertised on this campaign >>> site: http://www.python3statement.org/ >>> >>> Does anyone object to adopting this goal for Biopython, and >>> adding the project to http://www.python3statement.org/ ? >>> >>> Thanks, >>> >>> Peter _______________________________________________ Biopython-dev mailing list [email protected] http://mailman.open-bio.org/mailman/listinfo/biopython-dev