Path: csiph.com!news.mixmin.net!news.unit0.net!newsfeed.CARNet.hr!news.spin.it!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.maint.python Subject: Re: Matplotlib 3.0 - update ok? Date: Tue, 16 Oct 2018 09:10:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Oct 16 07:00:39 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.98 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, GMAIL=1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) X-Mailing-List: archive/latest/16446 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20181016070022.ltlhjnwh2etcw2e2@an3as.eu Approved: robomod@news.nic.it Lines: 42 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 16 Oct 2018 09:00:22 +0200 X-Original-Message-ID: <20181016070022.ltlhjnwh2etcw2e2@an3as.eu> X-Original-References: <47afc535-29be-9a2f-291f-37d790a618ad@uni-rostock.de> <20181016064615.7nja4gr4wffnf666@an3as.eu> <9a951bcf0467588fdd0b64dad002724c61980660.camel@gmail.com> Xref: csiph.com linux.debian.maint.python:11015 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). > > 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. -- http://fam-tille.de