Path: csiph.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!bofh.it!news.nic.it!robomod From: Robert Collins Newsgroups: linux.debian.maint.python Subject: Re: Removing some python3-* packages Date: Tue, 25 Aug 2015 00:50:01 +0200 Message-ID: References: X-Original-To: Barry Warsaw X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Aug 24 22:45:58 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: DYN_NJABL=SKIP(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5 BL_NJABL=SKIP(-1.5) CL_IP_EQ_HELO_IP=-2 (check from: .robertcollins. - helo: .mail-oi0-f42.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7 X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=/QBuMOVsLmC91rSchMMY09+EGfm/tZ+LpUkSFWjlQEs=; b=MTL0sZssEn7TsR3SK4O00ECPZBO+hhOr7lrWn9JYW6DGWTmXvNXplWHEDv7oSeqfbK KYoiz9pK65ZmEwTqWae51PWjdwLgRJAwl544ozzDjFbLoAIlgEGPUaqG2uv+OG+hmW2W U4y50DEhiqJfde+kNoEHaVZGL6785F4Ybfv9zlQ9GITDBjy8d33NE+skynhzLrwNdIa7 D7s0L5fws/Kfdw0v35ZLJJSU/dzREUPrOY1hO2LcE9NsRG5HKMIyVv4eNPCXze0Hu7yz aYbFZYOa4rVUYbDrHwwHf4STa9KmdEI8kBsPfcLLUCAUDd1WtWmC7SHErDWeWc5CcEak xtpg== X-Gm-Message-State: ALoCoQkA78ZyeKL3h/3Pem6am8EYZrFXQsc6dV82NIdM4GDg3iNhAWagtvHpwIwdKOcyBJiz6Bc8 MIME-Version: 1.0 X-Received: by 10.202.79.87 with SMTP id d84mr22362770oib.6.1440456341143; Mon, 24 Aug 2015 15:45:41 -0700 (PDT) X-Originating-IP: [122.57.103.106] Content-Type: text/plain; charset=UTF-8 X-Mailing-List: archive/latest/12519 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAJ3HoZ23K5z=CM9Xjc26qX9so7w9bzimctij_QKZi6JB+mzF_A@mail.gmail.com Approved: robomod@news.nic.it Lines: 41 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Debian Python X-Original-Date: Tue, 25 Aug 2015 10:45:41 +1200 X-Original-Message-ID: X-Original-References: <20150702155530.4e93b05d@limelight.wooz.org> <25C573EC-8BD4-4BB6-84EE-344C65343061@kitterman.com> <55D4B1BF.30505@debian.org> <20150824175757.236d2f23@anarchist.wooz.org> <20150824183701.37eb1b89@anarchist.wooz.org> Xref: csiph.com linux.debian.maint.python:7212 On 25 August 2015 at 10:37, Barry Warsaw wrote: > On Aug 25, 2015, at 10:03 AM, Robert Collins wrote: > >>On 25 August 2015 at 09:57, Barry Warsaw wrote: >>... >>> By all means, if there isn't any >>> significant difference between a standalone package and what's available in >>> the current supported Python 3 version, let's not ship unnecessary binary >>> packages. >> >>Even at the cost of having to patch upstream projects? > > Sorry, I'm not sure what the question means. Lets take Ironic. While it supports Python 2.7+ and 3.4+ it will depend on 'mock' for unit testing. If Debian has only Python 2.7 and 3.5 and wants to build Ironic for only Python 3.5 - which is a reasonable thing, then 'mock' is needed (because Ironic depends on 'mock'). We could: - patch Ironic to use unittest.mock on Python 3.5 - patch the stdlib to make 'mock' be an alias to unittest.mock - include 'python3-mock' as a binary package - not run the Ironic unit tests. Perhaps to you 'thing we package X uses library Y' implies 'binary package X is uncessary' - but the thing is that 'binary package X' may not be a significant difference vs the Python version in Debian at the time - even if there are significant differences vs older still upstream-supported Python versions - which is what the developer ecosystem will be referencing. -Rob -- Robert Collins Distinguished Technologist HP Converged Cloud