Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-08-06 Thread Chris Lamb
tags 904817 + pending thanks Fixed in Git, pending upload: https://salsa.debian.org/lintian/lintian/commit/51446673097e2a3f8e39f3ff6463db47ffc6bb52 checks/python.desc | 9 + checks/python.pm | 15

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-29 Thread Scott Kitterman
On July 29, 2018 7:39:53 AM UTC, Chris Lamb wrote: >Hey Scott, > >> You don't need to know. All you need to know is a package depends on >both. I >> don't think that there is any need to limit it to pyhon{3}-* >pacakges. > >Nod. :) > >(Oh, just in case I am parsing your '{3}' regex wrong,

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-29 Thread Chris Lamb
Hey Scott, > You don't need to know. All you need to know is a package depends on both. > I > don't think that there is any need to limit it to pyhon{3}-* pacakges. Nod. :) (Oh, just in case I am parsing your '{3}' regex wrong, it's currently limited to python-*, python2-* and python3-*,

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Scott Kitterman
On Sat, 28 Jul 2018 14:16:11 +0100 Chris Lamb wrote: > Hi Stuart, > > > In the upload of translate-toolkit 2.3.0-3, I ended up with the following: > > > > Depends: python3, python3-pkg-resources, python3-six, python3-translate, > > python3:any, python:any > > > > such that the package

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Stuart Prescott
On Saturday, 28 July 2018 15:58:55 AEST Chris Lamb wrote: > Hi Stuart, > > > > This won't trigger for packages unless they are called / > > > ^python([23]?)-/ however > > […] > > > Only module packages are called python{,3}-foo, while applications > > packages do not have the binary prefix > >

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Chris Lamb
Hi Stuart, > > This won't trigger for packages unless they are called / > > ^python([23]?)-/ however […] > Only module packages are called python{,3}-foo, while applications packages > do > not have the binary prefix Right, exactly; would your package have triggered this error *if* the

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Stuart Prescott
Hi Chris, > https://lintian.debian.org/tags/python-package-depends-on-package-from-othe > r-python-variant.html > > This won't trigger for packages unless they are called / > ^python([23]?)-/ however. Indeed, this seems to be required so we > "know" that a package is a "2" or a "3". > > Would

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Chris Lamb
Hi Stuart, > In the upload of translate-toolkit 2.3.0-3, I ended up with the following: > > Depends: python3, python3-pkg-resources, python3-six, python3-translate, > python3:any, python:any > > such that the package depended on both the Python 2 and Python 3 interpreters. Thinking about it,

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Stuart Prescott
Package: lintian Version: 2.5.94 Severity: wishlist Dear Maintainer, In the upload of translate-toolkit 2.3.0-3, I ended up with the following: Depends: python3, python3-pkg-resources, python3-six, python3-translate, python3:any, python:any such that the package depended on both the Python 2