Add Numba Python 2 timeline to Python3Statement

[CAM-Gerlach]

Given Numba already has a concrete timeline for dropping support for Python 2 by the EoL, I suggest adding the dates to Python3Statement, like most of the rest of the PyData stack have done, to make it easy for users to find in one central place and help accelerate Python 3 adoption.

[esc]

I made a pull-request here:

python3statement/python3statement.github.io#188

I left the timeline information deliberately vague, simply stating:

    'Numba':[
        {content: 'Python 2 & 3', start: '2012-03-08', end: '2019-12-31', py2:true},
        {content: 'Python 3 only', start: '2020-01-01', end: '2023-12-31'},
    ],

I choose to do this, because the timeline at https://numba.pydata.org/numba-doc/dev/reference/python27-eol.html states:

December 2018: Tag and release Numba 1.x.0. Create a Python 2.7 branch based on this release.

And we don't have a Numba 1 release yet.. We can however be pretty certain that we won't continue to support Python 2 beyond 2020-01-01.

[stuartarchibald]

Thanks for submitting a PR @esc, we can discuss this further in the core developer meeting tomorrow.

[CAM-Gerlach]

@stuartarchibald @seibert @esc Hey, any updates on this? Thanks!

[stuartarchibald]

@CAM-Gerlach not as yet, when a decision has been made the PR python3statement/python3statement.github.io#188 will be updated to reflect. Thanks.

[seibert]

We need to adjust our timeline here. I wanted to get through some of our backward compatibility-breaking changes before the final Python 2.7 release of Numba, but those have taken longer than we imagined a year ago. We'll have to address this next week when all of the core developers are available.

[sklam]

Python 2 is already removed from numba. Closing.