Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #11025

Re: Matplotlib 3.0 - update ok?

Path csiph.com!feeder.erje.net!2.eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!news.uzoreto.com!aioe.org!bofh.it!news.nic.it!robomod
From Arto Jantunen <viiru@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Matplotlib 3.0 - update ok?
Date Tue, 16 Oct 2018 11:30:01 +0200
Message-ID <wJtPP-2nU-11@gated-at.bofh.it> (permalink)
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> <wJrO1-1dS-7@gated-at.bofh.it> <wJsqK-1qy-17@gated-at.bofh.it> <wJsTM-1Po-3@gated-at.bofh.it> <wJtmN-1YR-3@gated-at.bofh.it> <wJtGa-2kV-5@gated-at.bofh.it>
X-Original-To debian-python@lists.debian.org
X-Mailbox-Line From debian-python-request@lists.debian.org Tue Oct 16 09:20:32 2018
Old-Return-Path <viiru@iki.fi>
X-Amavis-Spam-Status No, score=-5.73 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] autolearn=no autolearn_force=no
X-Policyd-Weight using cached result; rate: -8.1
X-Greylist delayed 2065 seconds by postgrey-1.36 at bendel; Tue, 16 Oct 2018 09:20:19 UTC
Mail-Followup-To debian-python@lists.debian.org
User-Agent Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
MIME-Version 1.0
Content-Type text/plain
X-Mailing-List <debian-python@lists.debian.org> archive/latest/16457
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/87pnwatfi1.fsf@iki.fi
Approved robomod@news.nic.it
Lines 43
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Tue, 16 Oct 2018 12:20:06 +0300
X-Original-Message-ID <87pnwatfi1.fsf@iki.fi>
X-Original-References <47afc535-29be-9a2f-291f-37d790a618ad@uni-rostock.de> <dc3af4878c155095129c0625cd260ea82758da20.camel@gmail.com> <20181016064615.7nja4gr4wffnf666@an3as.eu> <9a951bcf0467588fdd0b64dad002724c61980660.camel@gmail.com> <20181016070022.ltlhjnwh2etcw2e2@an3as.eu> <5be90e8cdf3630c8faeb6064894d223c140e9ab6.camel@gmail.com> <878t2ymjce.fsf@debian.org> <9ff36d3b19d86c938de54de91bda15cbb60d0126.camel@gmail.com> <87tvlmth36.fsf@iki.fi> <3b333117243a5b2bb180e2f2ba9d8db29b89e379.camel@gmail.com>
Xref csiph.com linux.debian.maint.python:11025

Show key headers only | View raw

ghisvail@gmail.com writes:

> On Tue, 2018-10-16 at 11:45 +0300, Arto Jantunen wrote:
>> 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).
>
> Oh, I see what you mean.
>
> So you'd have:
>
> - src:python-numpy-legacy providing python-numpy (<2.0) only
> - src:python-numpy providing python3-numpy (>=2.0) only
>
> Assuming version 2 is when the split happens.
>
> Am I correct?

Yeah, this would be my understanding of the plan. Things could get more
complex if the same split needs to happen at many levels of the stack (a
library that uses numpy is only compatible with numpy <2.0, followed by
another one on the next level down).

-- 
Arto Jantunen

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Matplotlib 3.0 - update ok? Steffen Möller <steffen.moeller@uni-rostock.de> - 2018-10-15 23:10 +0200
  Re: Matplotlib 3.0 - update ok? ghisvail@gmail.com - 2018-10-16 08:40 +0200
    Re: Matplotlib 3.0 - update ok? Andreas Tille <andreas@an3as.eu> - 2018-10-16 08:50 +0200
      Re: Matplotlib 3.0 - update ok? ghisvail@gmail.com - 2018-10-16 09:00 +0200
        Re: Matplotlib 3.0 - update ok? Andreas Tille <andreas@an3as.eu> - 2018-10-16 09:10 +0200
          Re: Matplotlib 3.0 - update ok? ghisvail@gmail.com - 2018-10-16 09:20 +0200
            Re: Matplotlib 3.0 - update ok? Ole Streicher <olebole@debian.org> - 2018-10-16 10:00 +0200
              Re: Matplotlib 3.0 - update ok? ghisvail@gmail.com - 2018-10-16 10:30 +0200
                Re: Matplotlib 3.0 - update ok? Arto Jantunen <viiru@debian.org> - 2018-10-16 11:00 +0200
                Re: Matplotlib 3.0 - update ok? ghisvail@gmail.com - 2018-10-16 11:20 +0200
                Re: Matplotlib 3.0 - update ok? Arto Jantunen <viiru@debian.org> - 2018-10-16 11:30 +0200
                Re: Matplotlib 3.0 - update ok? Michael Hudson-Doyle <michael.hudson@canonical.com> - 2018-10-16 12:10 +0200
    Re: Matplotlib 3.0 - update ok? Steffen Möller <steffen.moeller@uni-rostock.de> - 2018-10-16 10:40 +0200
      Re: Matplotlib 3.0 - update ok? ghisvail@gmail.com - 2018-10-16 10:50 +0200
      Re: Matplotlib 3.0 - update ok? Steffen Möller <steffen_moeller@gmx.de> - 2018-10-16 10:50 +0200
        Re: Matplotlib 3.0 - update ok? ghisvail@gmail.com - 2018-10-16 11:10 +0200
  Re: Matplotlib 3.0 - update ok? "W. Martin Borgert" <debacle@debian.org> - 2018-10-16 14:00 +0200
  Re: Matplotlib 3.0 - update ok? Sandro Tosi <morph@debian.org> - 2018-10-16 14:40 +0200

csiph-web