Re: Dropping Python 3.3 support soon?

Peter Cock <[email protected]> Mon, 19 Jun 2017 19:08:28 +0100
Newsgroups gmane.comp.python.bio.devel
Message-ID <CAKVJ-_5E99-pCpzGVKB+4AnXxWT7i2Q7ufz=pY_uC0FxLT-1sg__35974.3143119433$1497908491$gmane$org@mail.gmail.com>
That change has now been made, Biopython 1.70 will
not install under Python 3.3:

https://github.com/biopython/biopython/commit/8724f624eb6ac46dbe632ab2b57bee218466c22a

Also a follow up to remove some Python 3.3 only code:

https://github.com/biopython/biopython/commit/1d22a21e238dd6b82e597325acb256a5a60f8def

If there is any more bits of code only needed on early Python 3
(and not Python 2.7) which we remove, please get in touch.

Thanks,

Peter

On Wed, Jun 14, 2017 at 3:04 PM, Peter Cock <[email protected]> wrote:
> Dear Biopythoneers,
>
> In the absence of any objections, I propose to drop support
> for Python 3.3 later this week in preparation for the our next
> release, which will be Biopython 1.70
>
> Note that currently the most recent non-beta version of
> PyPy for Python 3 is still v5.5.0 which targeted Python 3.3
>
> http://doc.pypy.org/en/latest/index-of-release-notes.html#cpython-3-3-compatible-versions
> http://doc.pypy.org/en/latest/release-pypy3.3-v5.5.0.html
>
> However, since then all the PyPy releases for Python 3
> have targeted Python 3.5 (albeit only considered beta
> level releases):
>
> http://doc.pypy.org/en/latest/index-of-release-notes.html#cpython-3-5-compatible-versions
>
> Regards,
>
> Peter
>
> On Mon, Apr 10, 2017 at 4:57 PM, Peter Cock <[email protected]> wrote:
>> Dear Biopythoneers,
>>
>> Last year in June 2016 as part of the release of Biopython 1.67, we
>> declared support for Python 3.3 to be deprecated. This is coming
>> up on its one year anniversary, so in line with our deprecation policy
>> we could stop supporting Python 3.3 soon.
>>
>> http://biopython.org/wiki/Deprecation_policy
>>
>> Would anyone be upset about losing Python 3.3 support?
>>
>> (I'm not aware of any mainstream Linux distribution with Python 3.3
>> as the default, which would be a good reason to delay this.)
>>
>> Peter