Bug#829744: Add new-package-should-not-package-python2-module tag

To: Niels Thykier <niels@thykier.net>, 829744@bugs.debian.org
Cc: Scott Kitterman <debian@kitterman.com>
Subject: Bug#829744: Add new-package-should-not-package-python2-module tag
From: Chris Lamb <lamby@debian.org>
Date: Sat, 01 Oct 2016 12:18:29 +0100
Message-id: <[🔎] 1475320709.1835747.742714753.2DD3D4CC@webmail.messagingengine.com>
Reply-to: Chris Lamb <lamby@debian.org>, 829744@bugs.debian.org
In-reply-to: <5c1655a6-b0dd-a4a5-c456-5e45d5f67976@thykier.net>
References: <20971071.0MoWg4cfdg@kitterma-e6430> <20971071.0MoWg4cfdg@kitterma-e6430> <5c1655a6-b0dd-a4a5-c456-5e45d5f67976@thykier.net>

Niels Thykier wrote:

> I say we schedule this for December 2016 or early January 2017 then.

Can we have it "I:" now and "W:" then? :)

Python 2.7 is absolutely still supported throughout stretch (!) the here
idea is only to prevent unnecessary extra Python 2 packages by asking the
maintainer to pause for a moment before "automatically" packaging the
Python 2 version.


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Reply to: