11:22 p.m.
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 receive bug fixes until Python 2 is EOL.
So I'm wondering what exactly our plans are going forward for when the
final 3.0 release is made?
--
Elliott
3:19 p.m.
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 receive bug fixes until Python 2 is EOL.
So I'm wondering what exactly our plans are going forward for when the
final 3.0 release is made?
Is the 3 API substantially different from 2?
If not, I'd do what we did with ipython, astroid, pylint, astropy.
Create a python2-matplotib SRPM with the python2 package of matplotilb 2.
Remove python2 subpackage from python-matplotlib, update to 3.
If the API is changed a lot and we cannot update even on Python 3
without breaking everything, I suppose we could create python-matplotib2
with both stacks and again: remove python2 subpackage from
python-matplotlib, update to 3.
The python3-matplotib2 would need to be packaged a bit differently to
install to a separate location. This has been done for example with
python2-wxpython4. Consumers of matplotlib would need to slightly change
their packages.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
1:42 p.m.
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,
astropy.
Create a python2-matplotib SRPM with the python2 package of matplotilb 2.
Remove python2 subpackage from python-matplotlib, update to 3.
This seems to fell in this case.
Regards,
--
José Abílio
3:06 p.m.
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'd do what we did with ipython, astroid, pylint, astropy.
>
> Create a python2-matplotib SRPM with the python2 package of matplotilb 2.
> Remove python2 subpackage from python-matplotlib, update to 3.
This seems to fell in this case.
Should we try to package 3.0.0rc1 in Copr?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
10:36 a.m.
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 matplotilb 2.
Remove python2 subpackage from python-matplotlib, update to 3."
Unfortunately my testing time is very small as I am in holidays in family. :-)
Regards,
--
José Abílio
12:54 p.m.
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 determine
if this is F29 material.
Like what you have described above in the thread:
"Create a python2-matplotib SRPM with the python2 package of matplotilb 2.
Remove python2 subpackage from python-matplotlib, update to 3."
Unfortunately my testing time is very small as I am in holidays in family. :-)
I might eventually get to it. I just want to know if we are are all on
the same side.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
1:20 p.m.
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 release in 3 to 5 weeks (see the time difference between the last
rc release and the official release):
https://github.com/matplotlib/matplotlib/releases
Or can always ask to Thomas, the matplotlib leader. :-)
--
José Abílio
1:30 p.m.
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 previous releases I would expect
this to be release in 3 to 5 weeks (see the time difference between the last
rc release and the official release):
https://github.com/matplotlib/matplotlib/releases
Or can always ask to Thomas, the matplotlib leader. :-)
OK, let's just do this in rawhide only and only push to f29 if the
release is not too late?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
2:51 p.m.
On Fri, 17 Aug 2018 at 15:18, Miro Hrončok <mhroncok(a)redhat.com> 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 answer: when it is ready. :-)
>
> Now on more serious note and judging from the previous releases I would
expect
> this to be release in 3 to 5 weeks (see the time difference between the
last
> rc release and the official release):
> https://github.com/matplotlib/matplotlib/releases
>
> Or can always ask to Thomas, the matplotlib leader. :-)
OK, let's just do this in rawhide only and only push to f29 if the
release is not too late?
At the moment, there are some issues to work out with the new automatic
backend selection:
https://koji.fedoraproject.org/koji/taskinfo?taskID=29102643
but otherwise, I don't see any major issues.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
Elliott
3:52 p.m.
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.analyst(a)gmail.com> wrote:
On Fri, 17 Aug 2018 at 15:18, Miro Hrončok
<mhroncok(a)redhat.com> 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 answer: when it is ready. :-)
> >
> > Now on more serious note and judging from the previous releases I would
> expect
> > this to be release in 3 to 5 weeks (see the time difference between the
> last
> > rc release and the official release):
> > https://github.com/matplotlib/matplotlib/releases
> >
> > Or can always ask to Thomas, the matplotlib leader. :-)
>
> OK, let's just do this in rawhide only and only push to f29 if the
> release is not too late?
>
>
At the moment, there are some issues to work out with the new automatic
backend selection:
https://koji.fedoraproject.org/koji/taskinfo?taskID=29102643
but otherwise, I don't see any major issues.
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
>
--
Elliott
_______________________________________________
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedorapr...
--
Thomas Caswell
tcaswell(a)gmail.com
5:41 p.m.
On 17.8.2018 21:51, Elliott Sales de Andrade wrote:
On Fri, 17 Aug 2018 at 15:18, Miro Hrončok <mhroncok(a)redhat.com
<mailto:mhroncok@redhat.com>> 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 answer: when it is ready. :-)
>
> Now on more serious note and judging from the previous releases I
would expect
> this to be release in 3 to 5 weeks (see the time difference
between the last
> rc release and the official release):
> https://github.com/matplotlib/matplotlib/releases
>
> Or can always ask to Thomas, the matplotlib leader. :-)
OK, let's just do this in rawhide only and only push to f29 if the
release is not too late?
At the moment, there are some issues to work out with the new automatic
backend selection:
https://koji.fedoraproject.org/koji/taskinfo?taskID=29102643
but otherwise, I don't see any major issues.
Oh. So you have this ready? Can you open a WIP pull request for review?
I was just starting to dig into the specfile.
BTW I've invited you to https://github.com/fedora-python/matplotlib so
we can have the patches in Fedora manged github org.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
10:38 p.m.
On Fri, 17 Aug 2018 at 18:42, Miro Hrončok <mhroncok(a)redhat.com> wrote:
On 17.8.2018 21:51, Elliott Sales de Andrade wrote:
> On Fri, 17 Aug 2018 at 15:18, Miro Hrončok <mhroncok(a)redhat.com
> <mailto:mhroncok@redhat.com>> 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 answer: when it is ready. :-)
> >
> > Now on more serious note and judging from the previous releases I
> would expect
> > this to be release in 3 to 5 weeks (see the time difference
> between the last
> > rc release and the official release):
> > https://github.com/matplotlib/matplotlib/releases
> >
> > Or can always ask to Thomas, the matplotlib leader. :-)
>
> OK, let's just do this in rawhide only and only push to f29 if the
> release is not too late?
>
>
> At the moment, there are some issues to work out with the new automatic
> backend selection:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=29102643
> but otherwise, I don't see any major issues.
Oh. So you have this ready? Can you open a WIP pull request for review?
I was just starting to dig into the specfile.
Opened https://src.fedoraproject.org/rpms/python-matplotlib/pull-request/9
for 3.0.0rc2. I believe there are still issues with the backend tests.
BTW I've invited you to
https://github.com/fedora-python/matplotlib so
we can have the patches in Fedora manged github org.
Yep, I noticed that and have pushed the patches there already.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
Elliott
3:56 a.m.
On 29.8.2018 05:38, Elliott Sales de Andrade wrote:
On Fri, 17 Aug 2018 at 18:42, Miro Hrončok <mhroncok(a)redhat.com
<mailto:mhroncok@redhat.com>> wrote:
On 17.8.2018 21:51, Elliott Sales de Andrade wrote:
> On Fri, 17 Aug 2018 at 15:18, Miro Hrončok <mhroncok(a)redhat.com
<mailto:mhroncok@redhat.com>
> <mailto:mhroncok@redhat.com <mailto:mhroncok@redhat.com>>>
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 answer: when it is ready. :-)
> >
> > Now on more serious note and judging from the previous
releases I
> would expect
> > this to be release in 3 to 5 weeks (see the time difference
> between the last
> > rc release and the official release):
> > https://github.com/matplotlib/matplotlib/releases
> >
> > Or can always ask to Thomas, the matplotlib leader. :-)
>
> OK, let's just do this in rawhide only and only push to f29
if the
> release is not too late?
>
>
> At the moment, there are some issues to work out with the new
automatic
> backend selection:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=29102643
> but otherwise, I don't see any major issues.
Oh. So you have this ready? Can you open a WIP pull request for review?
I was just starting to dig into the specfile.
Opened
https://src.fedoraproject.org/rpms/python-matplotlib/pull-request/9 for
3.0.0rc2. I believe there are still issues with the backend tests.
Great! Who's working on python2-matplotib? I can help but I don't want
to maintain it.
BTW I've invited you to https://github.com/fedora-python/matplotlib so
we can have the patches in Fedora manged github org.
Yep, I noticed that and have pushed the patches there already.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
Elliott
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
4:10 a.m.
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 <mhroncok(a)redhat.com
> <mailto:mhroncok@redhat.com>> wrote:
>
> On 17.8.2018 21:51, Elliott Sales de Andrade wrote:
> > On Fri, 17 Aug 2018 at 15:18, Miro Hrončok <mhroncok(a)redhat.com
> <mailto:mhroncok@redhat.com>
> > <mailto:mhroncok@redhat.com <mailto:mhroncok@redhat.com>>>
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 answer: when it is ready. :-)
> > >
> > > Now on more serious note and judging from the previous
> releases I
> > would expect
> > > this to be release in 3 to 5 weeks (see the time difference
> > between the last
> > > rc release and the official release):
> > > https://github.com/matplotlib/matplotlib/releases
> > >
> > > Or can always ask to Thomas, the matplotlib leader. :-)
> >
> > OK, let's just do this in rawhide only and only push to f29
> if the
> > release is not too late?
> >
> >
> > At the moment, there are some issues to work out with the new
> automatic
> > backend selection:
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=29102643
> > but otherwise, I don't see any major issues.
>
> Oh. So you have this ready? Can you open a WIP pull request for
> review?
> I was just starting to dig into the specfile.
>
>
> Opened
> https://src.fedoraproject.org/rpms/python-matplotlib/pull-request/9
> for 3.0.0rc2. I believe there are still issues with the backend tests.
Great! Who's working on python2-matplotib? I can help but I don't want
to maintain it.
OK. Thanks everybody I've kicked the build for python-matplotlib 3
without python2 and python2-matplotlib 2. Rawhide only. Hopefully not
everything breaks.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
5:52 p.m.
On Fri, 21 Sep 2018 at 05:11, Miro Hrončok <mhroncok(a)redhat.com> 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 <mhroncok(a)redhat.com
>> <mailto:mhroncok@redhat.com>> wrote:
>>
>> On 17.8.2018 21:51, Elliott Sales de Andrade wrote:
>> > On Fri, 17 Aug 2018 at 15:18, Miro Hrončok <mhroncok(a)redhat.com
>> <mailto:mhroncok@redhat.com>
>> > <mailto:mhroncok@redhat.com
<mailto:mhroncok@redhat.com>>>
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 answer: when it is ready. :-)
>> > >
>> > > Now on more serious note and judging from the previous
>> releases I
>> > would expect
>> > > this to be release in 3 to 5 weeks (see the time
difference
>> > between the last
>> > > rc release and the official release):
>> > > https://github.com/matplotlib/matplotlib/releases
>> > >
>> > > Or can always ask to Thomas, the matplotlib leader. :-)
>> >
>> > OK, let's just do this in rawhide only and only push to f29
>> if the
>> > release is not too late?
>> >
>> >
>> > At the moment, there are some issues to work out with the new
>> automatic
>> > backend selection:
>> > https://koji.fedoraproject.org/koji/taskinfo?taskID=29102643
>> > but otherwise, I don't see any major issues.
>>
>> Oh. So you have this ready? Can you open a WIP pull request for
>> review?
>> I was just starting to dig into the specfile.
>>
>>
>> Opened
>> https://src.fedoraproject.org/rpms/python-matplotlib/pull-request/9
>> for 3.0.0rc2. I believe there are still issues with the backend tests.
>
> Great! Who's working on python2-matplotib? I can help but I don't want
> to maintain it.
OK. Thanks everybody I've kicked the build for python-matplotlib 3
without python2 and python2-matplotlib 2. Rawhide only. Hopefully not
everything breaks.
Thoughts on F29 then? I don't like to be 6 months behind. (Maybe wait for
3.0.1 which fixes some compatibility things.)
As for python2-matplotlib, I can commit to updating the test images (
https://github.com/QuLogic/mpl-images), but don't really want to own the
package. Maybe just leave it for @python-sig?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
Elliott
9:44 a.m.
On 26.9.2018 00:52, Elliott Sales de Andrade wrote:
On Fri, 21 Sep 2018 at 05:11, Miro Hrončok <mhroncok(a)redhat.com
<mailto:mhroncok@redhat.com>> 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 <mhroncok(a)redhat.com
<mailto:mhroncok@redhat.com>
>> <mailto:mhroncok@redhat.com <mailto:mhroncok@redhat.com>>>
wrote:
>>
>> On 17.8.2018 21:51, Elliott Sales de Andrade wrote:
>> > On Fri, 17 Aug 2018 at 15:18, Miro Hrončok
<mhroncok(a)redhat.com <mailto:mhroncok@redhat.com>
>> <mailto:mhroncok@redhat.com <mailto:mhroncok@redhat.com>>
>> > <mailto:mhroncok@redhat.com
<mailto:mhroncok@redhat.com>
<mailto:mhroncok@redhat.com <mailto:mhroncok@redhat.com>>>> 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 answer: when it is ready. :-)
>> > >
>> > > Now on more serious note and judging from the previous
>> releases I
>> > would expect
>> > > this to be release in 3 to 5 weeks (see the time
difference
>> > between the last
>> > > rc release and the official release):
>> > > https://github.com/matplotlib/matplotlib/releases
>> > >
>> > > Or can always ask to Thomas, the matplotlib
leader. :-)
>> >
>> > OK, let's just do this in rawhide only and only push
to f29
>> if the
>> > release is not too late?
>> >
>> >
>> > At the moment, there are some issues to work out with the new
>> automatic
>> > backend selection:
>> > https://koji.fedoraproject.org/koji/taskinfo?taskID=29102643
>> > but otherwise, I don't see any major issues.
>>
>> Oh. So you have this ready? Can you open a WIP pull request for
>> review?
>> I was just starting to dig into the specfile.
>>
>>
>> Opened
>> https://src.fedoraproject.org/rpms/python-matplotlib/pull-request/9
>> for 3.0.0rc2. I believe there are still issues with the backend
tests.
>
> Great! Who's working on python2-matplotib? I can help but I don't
want
> to maintain it.
OK. Thanks everybody I've kicked the build for python-matplotlib 3
without python2 and python2-matplotlib 2. Rawhide only. Hopefully not
everything breaks.
Thoughts on F29 then? I don't like to be 6 months behind. (Maybe wait
for 3.0.1 which fixes some compatibility things.)
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.
IMHO the main purpose of matplotlib in the RPM package is to support
other RPM packages. Developers who want the new stuff can use venv+pip.
Is there any serious trouble with matplotlib 2 that would justify the
update?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
9:17 a.m.
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 support
other RPM packages. Developers who want the new stuff can use venv+pip.
Every time that I read this I always remember Jamie Zawinski's quote:
Some people, when confronted with a problem, think "I know, I'll use regular
expressions." Now they have two problems.
https://en.wikiquote.org/wiki/Jamie_Zawinski
Is there any serious trouble with matplotlib 2 that would justify
the
update?
IMHO it is more the other way around, with our emphasis on python 3 for
Fedora 29+ matplotlib 3.0.0 is the first release to fully go into python 3
that would align both goals.
All IMHO, of course. :-)
--
José Abílio
2029
days inactive
2077
days old
python-devel@lists.fedoraproject.org
16 comments
4 participants
participants (4)
-
Elliott Sales de Andrade -
José Abílio Matos -
Miro Hrončok -
Thomas Caswell