[Matplotlib-devel] Long term release schedule

[Matthias Bussonnier]

Hey,

On Mon, May 16, 2016 at 10:51 AM, Nathan Goldbaum <nathan12343 at gmail.com> wrote:

> Another concern: if I depend on matplotlib and don't want to drop python2
> support (but also don't want to drop support for newer matplotlib versions),
> that means I need to simultaneously support the last py2 matplotlib through
> the latest and greatest matplotlib version on py3. It would be nice if some
> thought could be expended for the breaking changes you're planning on
> matplotlib 3.0 so that compatibility across matplotlib versions can be
> attained without a huge amount of trouble.
>

As a data point, we don't planned to break the API for IPython 6.0
more than usual.
Though there are some things (liek completion) were we'd really like to break
API/provide a new one.

Though there are some things that will be hard to impossible to backport.

As Thomas said, if someone[user or company] come up and want to backport
all the things or provide shims, we'll likely not say no, but there is
few chance we actually
publish that under the 'IPython' package name.

>>
>> I suspect you will have two wave of people pissed:
>> When you switch master to 3+ only, and when you **release** a 3+ only
>> version.
>> You'll have **some** packaging pain, as you need to publish a `tar.gz`
>> and `zip` that pip should not even **try** to install on Python 2.
>>
>> As for undoubtedly following, I would not be so sure. I can see pandas
>> and numpy be one of the last projects dropping support.
>> Especially numpy which is at the base of most of the SciPy Stack.
>>
>> Though, having **their dependents** being python 3 only will likely
>> make their decision much easier.
>>
>> Will mercurial ever migrate to Py3... I'm not sure, but we can argue
>> it's not in the Scientific stack.
>
>
> This is being actively worked on.

Ah, I didn't knew that, but this comment was mostly meant as a joke as Mercurial
was IIUC known to have often been against migrating its codebase to Python 3.
And yes, I know I can link the executable.

-- 
M