On 26.9.2018 00:52, Elliott Sales de Andrade wrote:
On Fri, 21 Sep 2018 at 05:11, Miro Hrončok <mhron...@redhat.com
<mailto:mhron...@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 <mhron...@redhat.com
<mailto:mhron...@redhat.com>
>> <mailto:mhron...@redhat.com <mailto:mhron...@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
<mhron...@redhat.com <mailto:mhron...@redhat.com>
>> <mailto:mhron...@redhat.com <mailto:mhron...@redhat.com>>
>> > <mailto:mhron...@redhat.com <mailto:mhron...@redhat.com>
<mailto:mhron...@redhat.com <mailto:mhron...@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
_______________________________________________
python-devel mailing list -- python-de...@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@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-de...@lists.fedoraproject.org
