Re: Plans for Matplotlib 3.0+

2018-09-29 Thread José Abílio Matos
On Wednesday, 26 September 2018 00.35.32 WEST Miro Hrončok wrote: > I would rather not. The package split wasn't properly tested and F29 is > almost out. This isn't something to stick in between Beta and Final. That I understand. :-) > IMHO the main purpose of matplotlib in the RPM package is to

Re: Plans for Matplotlib 3.0+

2018-09-25 Thread Elliott Sales de Andrade
On Fri, 21 Sep 2018 at 05:11, Miro Hrončok wrote: > On 29.8.2018 10:56, Miro Hrončok wrote: > > On 29.8.2018 05:38, Elliott Sales de Andrade wrote: > >> On Fri, 17 Aug 2018 at 18:42, Miro Hrončok >> > wrote: > >> > >> On 17.8.2018 21:51, Elliott Sales de Andrade w

Re: Plans for Matplotlib 3.0+

2018-09-21 Thread Miro Hrončok
On 29.8.2018 10:56, Miro Hrončok wrote: On 29.8.2018 05:38, Elliott Sales de Andrade wrote: On Fri, 17 Aug 2018 at 18:42, Miro Hrončok > wrote:     On 17.8.2018 21:51, Elliott Sales de Andrade wrote: > On Fri, 17 Aug 2018 at 15:18, Miro Hrončok mailto:mhron...@r

Re: Plans for Matplotlib 3.0+

2018-08-29 Thread Miro Hrončok
On 29.8.2018 05:38, Elliott Sales de Andrade wrote: On Fri, 17 Aug 2018 at 18:42, Miro Hrončok > wrote: On 17.8.2018 21:51, Elliott Sales de Andrade wrote: > On Fri, 17 Aug 2018 at 15:18, Miro Hrončok mailto:mhron...@redhat.com> >

Re: Plans for Matplotlib 3.0+

2018-08-28 Thread Elliott Sales de Andrade
On Fri, 17 Aug 2018 at 18:42, Miro Hrončok wrote: > On 17.8.2018 21:51, Elliott Sales de Andrade wrote: > > On Fri, 17 Aug 2018 at 15:18, Miro Hrončok > > wrote: > > > > > > > > On 17.8.2018 20:20, José Abílio Matos wrote: > > > On Friday, 17 August 2018 18.5

Re: Plans for Matplotlib 3.0+

2018-08-17 Thread Miro Hrončok
On 17.8.2018 21:51, Elliott Sales de Andrade wrote: On Fri, 17 Aug 2018 at 15:18, Miro Hrončok > wrote: On 17.8.2018 20:20, José Abílio Matos wrote: > On Friday, 17 August 2018 18.54.59 WEST Miro Hrončok wrote: >> Is there an upstream schedule? That wo

Re: Plans for Matplotlib 3.0+

2018-08-17 Thread Thomas Caswell
I agree with Elliot, the only thing I expect any major issues with is the backend selection. 3-5 weeks is the likely timeline. Tom On Fri, Aug 17, 2018 at 4:38 PM Elliott Sales de Andrade < quantum.anal...@gmail.com> wrote: > On Fri, 17 Aug 2018 at 15:18, Miro Hrončok wrote: > >> >> >> On 17.8

Re: Plans for Matplotlib 3.0+

2018-08-17 Thread Elliott Sales de Andrade
On Fri, 17 Aug 2018 at 15:18, Miro Hrončok wrote: > > > On 17.8.2018 20:20, José Abílio Matos wrote: > > On Friday, 17 August 2018 18.54.59 WEST Miro Hrončok wrote: > >> Is there an upstream schedule? That would very much help us to determine > >> if this is F29 material. > > > > You know the ans

Re: Plans for Matplotlib 3.0+

2018-08-17 Thread Miro Hrončok
On 17.8.2018 20:20, José Abílio Matos wrote: On Friday, 17 August 2018 18.54.59 WEST Miro Hrončok wrote: Is there an upstream schedule? That would very much help us to determine if this is F29 material. You know the answer: when it is ready. :-) Now on more serious note and judging from the

Re: Plans for Matplotlib 3.0+

2018-08-17 Thread José Abílio Matos
On Friday, 17 August 2018 18.54.59 WEST Miro Hrončok wrote: > Is there an upstream schedule? That would very much help us to determine > if this is F29 material. You know the answer: when it is ready. :-) Now on more serious note and judging from the previous releases I would expect this to be r

Re: Plans for Matplotlib 3.0+

2018-08-17 Thread Miro Hrončok
On 17.8.2018 17:36, José Abílio Matos wrote: On Monday, 13 August 2018 21.06.03 WEST Miro Hrončok wrote: Should we try to package 3.0.0rc1 in Copr? Yes, in the sense that it would be interesting to have this in Fedora 29. :-) Is there an upstream schedule? That would very much help us to det

Re: Plans for Matplotlib 3.0+

2018-08-17 Thread José Abílio Matos
On Monday, 13 August 2018 21.06.03 WEST Miro Hrončok wrote: > Should we try to package 3.0.0rc1 in Copr? Yes, in the sense that it would be interesting to have this in Fedora 29. :-) Like what you have described above in the thread: "Create a python2-matplotib SRPM with the python2 package of mat

Re: Plans for Matplotlib 3.0+

2018-08-13 Thread Miro Hrončok
On 13.8.2018 20:42, José Abílio Matos wrote: On Sunday, 12 August 2018 21.19.39 WEST Miro Hrončok wrote: Is the 3 API substantially different from 2? Nope, it is the (natural) evolution of matplotlib 2. For further details see: https://matplotlib.org/devdocs/users/whats_new.html If not, I'

Re: Plans for Matplotlib 3.0+

2018-08-13 Thread José Abílio Matos
On Sunday, 12 August 2018 21.19.39 WEST Miro Hrončok wrote: > Is the 3 API substantially different from 2? Nope, it is the (natural) evolution of matplotlib 2. For further details see: https://matplotlib.org/devdocs/users/whats_new.html > If not, I'd do what we did with ipython, astroid, pylint,

Re: Plans for Matplotlib 3.0+

2018-08-12 Thread Miro Hrončok
On 12.8.2018 06:22, Elliott Sales de Andrade wrote: Hi all, In case you weren't aware, Matplotlib 3.0 will drop support for Python 2. The rc1 was just released today/yesterday, though I have not yet attempted to see how that update will go. The 2.2.x line will continue to be supported and rec