Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Michael Hudson-Doyle Newsgroups: linux.debian.maint.python Subject: Re: Matplotlib 3.0 - update ok? Date: Tue, 16 Oct 2018 12:10:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Oct 16 10:00:10 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.98 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, EMPTY_BODY=3, GMAIL=1, HTML_MESSAGE=2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_HI=-5] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .canonical. - helo: .youngberry.canonical. - helo-domain: .canonical.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7 X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TwYhpqHvqSvH5v6NCdjf2zhQQkrnGX9fEjM7EEKYAd4=; b=ABSgPVYQMFG+m8xsFFkh0ougE8+aQ/GnbtbdUZyjSJ2p1zk/HN2OnaP499Icmy3Us6 /GWL/QYHsv2TyVuKAK+aTe5tkr4ptknfE6qQjCXV4PxYsUVu18AGS0jgy0UMh4hxl5Zw SCUkLzHVQ74/d/TyoERu853Vxs+fGfFHgeDfBOMTlgiZsVe1W+Y5oAo4Svt4noKzoFcs ZFk6TrPKAOXvIbNDq1Ty/LYs7dVLSaZTBC/1OQqDBOjcXOok19AYAsKltKdUjgOE2dlg iuNEvfbkr0mwTwhF3C5/Kg5se0AxyYmg48dWHg7Wo9g+cN/rj3wU0nDK4a1LHlnlKiKX XgLQ== X-Gm-Message-State: ABuFfohqOG3FqAOLG9jkK66JCmx0/vM9mOzzzer1zH0QvygwcgDZRsSr y19NEhctOJgREu3x0QJLLD8vLX98ySGiq6yXs7yy3lllOkWesZ91DvnAUbrw99SiabyZKHmcRyI uykXKQob1JvSmr0956Es3D08GZvO+bkvosjMcQc/1Ne1mOy2Fb8aIUqYOObD8 X-Received: by 2002:a9d:24c7:: with SMTP id z65mr13063536ota.229.1539682911659; Tue, 16 Oct 2018 02:41:51 -0700 (PDT) X-Google-SMTP-Source: ACcGV61yI2PlhTAcclRU801+kjqoFEiezcBgjk6QmkkE70i+60FgkaMk3PUidjeWEmyiQ5magWLW+xao39vk1lwsUhw= X-Received: by 2002:a9d:24c7:: with SMTP id z65mr13063530ota.229.1539682911397; Tue, 16 Oct 2018 02:41:51 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000000453d0578555dd9" X-Mailing-List: archive/latest/16458 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAJ8wqtdFQWb_oYJQr80wbMQZkfji6oS6q_mE83L_i9xFC+eAZA@mail.gmail.com Approved: robomod@news.nic.it Lines: 95 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: viiru@debian.org, debian-python X-Original-Date: Tue, 16 Oct 2018 22:41:39 +1300 X-Original-Message-ID: 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> <87tvlmth36.fsf@iki.fi> <3b333117243a5b2bb180e2f2ba9d8db29b89e379.camel@gmail.com> Xref: csiph.com linux.debian.maint.python:11026 --00000000000000453d0578555dd9 Content-Type: text/plain; charset="UTF-8" On Tue, 16 Oct 2018 at 22:11, wrote: > 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 > This sort of thing has already happened for astroid, src:astroid builds python3-astroid 2.0.4-2 and src:astroid2 builds python-astroid 1.6.5-2 (and something similar for pylint). Cheers, mwh --00000000000000453d0578555dd9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue= , 16 Oct 2018 at 22:11, <ghisvail@= gmail.com> wrote:
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,<= br> > > introducing new legacy packages for Python 2, and patching the > > large
> > collection of packages relying on the Python 2 versions of these<= br> > > 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<= br> > and python3-numpy, built from a source package called python-numpy. > In
> my understanding the proposed change is to keep having the exact same<= br> > 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 (>=3D2.0) only

This sort of thing has already happened for astroid, = src:astroid builds python3-astroid 2.0.4-2 and src:astroid2 builds python-a= stroid 1.6.5-2 (and something similar for pylint).

Cheers,
mwh=C2=A0
--00000000000000453d0578555dd9--