Re: Matplotlib 3.0 - update ok?

[ghisvail@gmail.com]

On Tue, 2018-10-16 at 08:46 +0200, Andreas Tille wrote:
> On Tue, Oct 16, 2018 at 07:30:55AM +0100, ghisvail@gmail.com wrote:
> > > Any opinions from your sides?
> > 
> > How is that going to work without creating package conflicts?
> > 
> > I suppose  the main module is still named "matplotlib" not
> > "matplotlib3" in version 3 onwards? So using python3-matplotlib3
> > would
> > be a breach of policy.
> 
> Probably.

Described in Section 2.2 of the Debian Python policy.

> > Let me ask you this: where is the rush to package this machine
> > learning
> > library? Could it wait after the Buster release cycle, where we
> > might
> > be in a more comfortable position to upgrade matplotlib?
> 
> I'm not sure what might be the difference between:
> 
>    3.0.0 Stable version
>    2.2.3 LTS LTS version
> 
> We have some months left until freeze so may be right now it is not
> to
> late to package what upstream considers stable.
> 
> Kind regards
> 
>       Andreas.


>From the upstream homepage: "Matplotlib 3.0 is Python 3 only."

Afaik, Python 2 is still considered relevant for the Buster release
cycle. Hence why I am suggesting to wait for the next release cycle
before upgrading key scientific packages, such as matplotlib, to Python
3 only.

Cheers,
Ghis