Bug#829744: Add new-package-should-not-package-python2-module tag
On Wed, 06 Jul 2016 01:06:57 +0200 Chris Lamb <lamby@debian.org> wrote:
> Mattias Klose wrote:
>
> > Please only trigger this warning if no corresponding
> > python3 module is uploaded (at least until after the
> > stretch release).
>
> Are we sure? The idea is to dissuade the Python 2 module from being
> packaged in the first place (on the principle that it is one less to
> remove later) rather than to promote that the Python 3 module is
> also packaged.
>
> Otherwise this tag's semantics are really along the lines of "don't
> forget to package the Python 3 version!" which is already somewhat
> implicit in the ecosystem and causes us more work down the road.
If that's the case, then it's premature before the freeze. Python2.7 is
'supported' through the expected stretch lifetime, so I don't see it being
anything other than a maintainer call. For the next release, it'll maybe be
different.
Scott K
Reply to: