Skip to content

when should we drop support for legacy python 2? #765

@anthrotype

Description

@anthrotype

Python 3.6 is coming out in a couple of weeks with loads of new cool features.
Alas, we are still stuck with supporting legacy Python 2.7.

I think we need to start thinking about until when we would like to keep support for legacy Python.

We can't keep stretching the code -- as well as ourselves -- for long, trying to maintain compatibility with such diverse languages.

The main issue we face is that font editors (mostly OSX based) that require fonttools and sister libraries, have so far contented themselves to link their apps with the Apple-provided Python 2.7 framework. Of course, we can't know when exactly Apple will finally decide to ship a modern Python with macOS.

However, it's not difficult to bundle a Python distribution along with the font editors themselves (e.g., I found a blog post explaining how to do that, and doesn't sound that complicated). I'm also willing to lend my spare time to help font editors developers making this happen.

So, I propose we set the end-of-support date one year from now, on 12 December 2017.

WDYT?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions