Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: ghisvail@gmail.com
Newsgroups: linux.debian.maint.python
Subject: Re: Matplotlib 3.0 - update ok?
Date: Tue, 16 Oct 2018 09:20:01 +0200
Message-ID: <wJrO1-1dS-7@gated-at.bofh.it>
References: <wJihH-412-7@gated-at.bofh.it> <wJrbj-LD-1@gated-at.bofh.it> <wJrkZ-OP-1@gated-at.bofh.it> <wJruF-S0-11@gated-at.bofh.it> <wJrEl-1aA-3@gated-at.bofh.it>
Old-Return-Path: <ghisvail@gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.1-1
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Approved: robomod@news.nic.it
Lines: 54
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:11016

On Tue, 2018-10-16 at 09:00 +0200, Andreas Tille wrote:
> On Tue, Oct 16, 2018 at 07:55:40AM +0100, ghisvail@gmail.com wrote:
> > > > 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.
> 
> Depending how heavy Steffen would volunteer to patch and also rename
> the
> module (which I would not consider a very sensible idea).

Which means future packages depending on matplotlib v3+ would have to
be manually patched to account for the renaming. Sounds impractical to
me.

> > > 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.
> 
> Right.  This would surely kick several scientific packages.
> 
> Kind regards
> 
>       Andreas. 

Indeed. Note that NumPy has already published plans to become Python 3
only in the near future, so the deprecation of Python 2 in the
scientific stack will happen eventually.

I just don't think it should be rushed into the Buster release cycle.

Ghis