Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Arto Jantunen Newsgroups: linux.debian.maint.python Subject: Re: Matplotlib 3.0 - update ok? Date: Tue, 16 Oct 2018 11:00: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 08:52:36 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.937 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, GMAIL=1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RDNS_NONE=0.793] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -8.1 X-Greylist: delayed 358 seconds by postgrey-1.36 at bendel; Tue, 16 Oct 2018 08:52:23 UTC User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Mailing-List: archive/latest/16454 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87tvlmth36.fsf@iki.fi Approved: robomod@news.nic.it Lines: 19 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 16 Oct 2018 11:45:49 +0300 X-Original-Message-ID: <87tvlmth36.fsf@iki.fi> X-Original-References: <47afc535-29be-9a2f-291f-37d790a618ad@uni-rostock.de> <20181016064615.7nja4gr4wffnf666@an3as.eu> <9a951bcf0467588fdd0b64dad002724c61980660.camel@gmail.com> <20181016070022.ltlhjnwh2etcw2e2@an3as.eu> <5be90e8cdf3630c8faeb6064894d223c140e9ab6.camel@gmail.com> <878t2ymjce.fsf@debian.org> <9ff36d3b19d86c938de54de91bda15cbb60d0126.camel@gmail.com> Xref: csiph.com linux.debian.maint.python:11022 ghisvail@gmail.com writes: > Don't get me wrong, I am all in favour for a modern stack, including > Python 3. > > However, upgrading NumPy et al. to their Python 3 only versions, > introducing new legacy packages for Python 2, and patching the large > collection of packages relying on the Python 2 versions of these sounds > like a lot of work for the time we have got left in the Buster release > cycle. In my understanding there is no need to patch any of the reverse dependencies. Currently there are binary packages called python-numpy and python3-numpy, built from a source package called python-numpy. In my understanding the proposed change is to keep having the exact same binary packages, just built from two different source packages (python-numpy and python-numpy-legacy or whatever). -- Arto Jantunen