[Matplotlib-devel] Long term release schedule

Thomas Caswell tcaswell at gmail.com
Mon May 16 14:09:32 EDT 2016

I think it is fair to expect that the 3.x series only adds functionality,
but does not remove any APIs.

Part of this exercise is to really sort out what the 2.7 demand really is.
If someone shows up and commits to backporting all new features from 3.x to
2.x I would not be opposed.


On Mon, May 16, 2016 at 1:54 PM Nathan Goldbaum <nathan12343 at gmail.com>

> On Mon, May 16, 2016 at 12:42 PM, Matthias Bussonnier <
> bussonniermatthias at gmail.com> wrote:
>> On Sun, May 15, 2016 at 1:45 PM, Fabien <fabien.maussion at gmail.com>
>> wrote:
>> >
>> > What would be more interesting to read are arguments against this
>> > initiative. But I believe that once the major projects (mpl, jupyter,
>> > ipython, pandas...) have made the first step, others will undoubtedly
>> > follow.
>> Devil's advocate: You will piss of some people that will either stop
>> contributing, or fork MPL, and get an indefinite
>> number of bug report from people stuck on the last version supporting
>> 2.7.
> 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.
>> 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.
> In any case, even if mercuroal doesn't move to python3, you can very
> easily have a separate python2 installation. You can even do this with
> conda and just symlink the hg executable into your python3 environment.
>> --
>> M
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160516/2cc7c240/attachment-0001.html>

More information about the Matplotlib-devel mailing list