Path: csiph.com!4.us.feeder.erje.net!feeder.erje.net!2.eu.feeder.erje.net!news.unit0.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 11:20:02 +0200 Message-ID: References: X-Original-To: Arto Jantunen , debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Oct 16 09:11:13 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.442 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001, SARE_MSGID_LONG40=0.637] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -7 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=/0C9mPWFHKPeRbqSxKFCbkSCH747Hew+zKr342yFq+k=; b=D5+1lIMao05A77a90+XGEv9MaCIFPuhum5rl85zyVelRADx8i6wOUbodHq7JK7waRs +BA/NtIEfAW+CXgL8BhtD+zDpx2Z8G3fSaFq+IsGuVzUH/+Iul3kWOY9ziR7dO+dsfMz 4cgE4ESv0DD2fgHxeTRcUdakoK2vpiRC4fxVZsI7L/3/paIuvVH8drUgwuonjXiN84ml Gkxojns7NxlYnrIb6keZ43a29vvEjqqrvMqiZVCqlrQf/hU51RsdWludQT2W3sRPeHog Ey4sNVGB0LhidFyvgvhY1pzXfXm17HCWGePJnsI3dXb5/5jCe+71KbObKRWM+osGka+u A0NQ== X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=/0C9mPWFHKPeRbqSxKFCbkSCH747Hew+zKr342yFq+k=; b=rRU1hRezu/P8y3KoVV/vUL2mOsHz4txuFeSpzYuwLMMVago9s/gMQ3/KxtqoB3IPiT 76wPQU0HricAxzslEUyO9sHy32nUf8MlKkp2ZcpEm5OVGLvjUkPcsTVtifEX2f3UpnqL jAR0v2NDj+gQrT+i+HYI0p2ffS1UZNPAu8qB+WUgPQcvp1xht9Tf/q6AJeaqLnZlxa7G QnYN1zYqOxNPrVZQvl0koiEqaZQtr4Vood3/YWD88pYSn0WpvMwdhs1L9wknB+2QJW6c U4KwdKTTRcyNuQuxzZNBANw1KzUJADw7iST+s/eWpZWY36/p1IDb1bDeCVzYwwsSyvBT fH5g== X-Gm-Message-State: ABuFfoi0pZQzcqdg4FbvP0JEVNAO1fNNDrPd1Gb+ig1iL7w3sQ3BrhvE CYiHsQH1WXU9n2aXnEYe69cSZH6p X-Google-SMTP-Source: ACcGV62lRoGDVPHXKdN7W/mwfzfs4QaWjkXLNu4RobyPPR1c456ljKNoXmlgprV6Kzb43l6EWyXbwA== X-Received: by 2002:adf:e403:: with SMTP id g3-v6mr16809321wrm.96.1539681044532; Tue, 16 Oct 2018 02:10:44 -0700 (PDT) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.1-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/16456 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/3b333117243a5b2bb180e2f2ba9d8db29b89e379.camel@gmail.com Approved: robomod@news.nic.it Lines: 35 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 16 Oct 2018 10:10:42 +0100 X-Original-Message-ID: <3b333117243a5b2bb180e2f2ba9d8db29b89e379.camel@gmail.com> 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> Xref: csiph.com linux.debian.maint.python:11024 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? Ghis