[Matplotlib-devel] Long term release schedule

[Benjamin Root]

I think this timeline is reasonable, and it is especially important that we
express this now, so that various members of the python community can use
these statements as evidence to their management that it is time to begin
the transition process in their enterprise.

In my company, one of the things holding us back is the amount of code that
has little if any unit tests. For the codebases that do have decent
coverage, our usage of CI is spotty. So, we target a particular platform
and we never get much opportunity to automatically test other platforms to
ensure that our changes aren't py3k-breaking. What is changing is that
GitLab is improving its CI interface, so -- hopefully -- it'll get better
soon.

If it doesn't, then I guess I'll become the resident py2.7 supporter...

Ben Root


On Sun, May 15, 2016 at 4:45 PM, Fabien <fabien.maussion at gmail.com> wrote:

> On 05/14/2016 08:15 PM, Thomas Caswell wrote:
>
>>
>> Not sure if silence means you all agree or disagree so badly that no one
>> can compose a polite email ;).
>>
>
> I totally agree, but I think that my opinion is not very useful in that
> case ;-)
>
> 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.
>
> Fabien
>
>
>
>
>
>
> _______________________________________________
> 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/77a470c0/attachment-0001.html>