Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-15 Thread Thomas Goirand
On 10/15/19 7:08 PM, Sandro Tosi wrote: > On Tue, Oct 15, 2019 at 12:55 PM Thomas Goirand wrote: >> >> On 10/15/19 5:00 AM, Craig Small wrote: >>> >>> >>> On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, >> > wrote: >>> >>> Please re-read the excellent contribution from

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-15 Thread Sandro Tosi
On Tue, Oct 15, 2019 at 12:55 PM Thomas Goirand wrote: > > On 10/15/19 5:00 AM, Craig Small wrote: > > > > > > On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, > > wrote: > > > > Please re-read the excellent contribution from Neil Williams > > in this thread, and

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-15 Thread Thomas Goirand
On 10/15/19 5:00 AM, Craig Small wrote: > > > On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, > wrote: > > Please re-read the excellent contribution from Neil Williams > in this thread, and explain again why we have a special case... :) > > I just did re-read it;

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-15 Thread Sandro Tosi
On Mon, Oct 14, 2019 at 10:14 PM Thomas Goirand wrote: > > On 10/14/19 3:54 PM, Sandro Tosi wrote: > >>> But in both cases, it's going to take a very long time. Do we really > >>> want to get stuck on these packages for like forever, or would it feel > >>> ok to raise the severity to serious, so

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Craig Small
On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, wrote: > Please re-read the excellent contribution from Neil Williams > in this thread, and explain again why we have a special case... :) I just did re-read it; especially about it's RC bugs not a total removal RM so these packages will sit in

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Craig Small
On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, wrote: > > Either we don't have enough details about net-snmp, or you're trying to > push for not-valid-yet-another-exception. > It's more if a source package makes multiple binary packages, one of those being a python 2 package, and there are other

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Thomas Goirand
On 10/14/19 3:54 PM, Sandro Tosi wrote: >>> But in both cases, it's going to take a very long time. Do we really >>> want to get stuck on these packages for like forever, or would it feel >>> ok to raise the severity to serious, so that the package gets >>> auto-removed and then we can work on

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Thomas Goirand
On 10/14/19 11:05 PM, Craig Small wrote: > Hi All, >   Just be careful with the bugs severity on complicated packages. I > totally get the python only packages that produce a single binary, go > for it for those. > > However consider the net-snmp python module. It's python 2 only and > upstream

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Craig Small
Hi All, Just be careful with the bugs severity on complicated packages. I totally get the python only packages that produce a single binary, go for it for those. However consider the net-snmp python module. It's python 2 only and upstream isn't changing it. In fact I am pretty sure they don't

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Neil Williams
On Mon, 14 Oct 2019 20:22:40 +0200 Gregor Riepl wrote: > Oh, and by the way, I just saw this: > https://github.com/kovidgoyal/calibre/blob/master/README.python3 > > Perhaps a working Py3 port is not so far off after all. > Then it can be introduced as a new upload when it is ready. It's not

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Neil Williams
On Mon, 14 Oct 2019 20:18:10 +0200 Gregor Riepl wrote: > > As of now, calibre is not of sufficient quality to be part of a > > Debian release and until it drops all Python2 requirements, it must > > be considered RC buggy. > > Is your quality argument based on the Calibre author's

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Gregor Riepl
Oh, and by the way, I just saw this: https://github.com/kovidgoyal/calibre/blob/master/README.python3 Perhaps a working Py3 port is not so far off after all.

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Gregor Riepl
> As of now, calibre is not of sufficient quality to be part of a Debian release > and until it drops all Python2 requirements, it must be considered RC buggy. Is your quality argument based on the Calibre author's shenanigans?

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Andrey Rahmatullin
On Mon, Oct 14, 2019 at 09:54:18AM -0400, Sandro Tosi wrote: > i think it's a bit premature to raise severity to RC (we should also > check with the release team): these bugs have been opened since just 2 > months and a half, and the development cycle for bullseye started not > longer before.

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Ondrej Novy
Hi, po 14. 10. 2019 v 4:52 odesílatel Thomas Goirand napsal: > But in both cases, it's going to take a very long time. Do we really > want to get stuck on these packages for like forever, or would it feel > ok to raise the severity to serious, so that the package gets > auto-removed and then we

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-14 Thread Neil Williams
On Sun, Oct 13, 2019 at 11:41:38PM -0400, Nicholas D Steeves wrote: > Hi Thomas and Python Team, > > Thomas Goirand writes: > > > For example, today I looked into removing Python 2 from python-cogent. > > Running sixer on all files lead to a huge log of problems to solve by > > hand. There's no

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-13 Thread Scott Kitterman
On Sunday, October 13, 2019 10:52:17 PM EDT Thomas Goirand wrote: > Hi, > > In some cases I've seen, particularly in the med or science team, > switching some packages to Python 3 requires a significant effort. > > For example, today I looked into removing Python 2 from python-cogent. > Running

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-13 Thread Nicholas D Steeves
Hi Thomas and Python Team, Thomas Goirand writes: > For example, today I looked into removing Python 2 from python-cogent. > Running sixer on all files lead to a huge log of problems to solve by > hand. There's no upstream support for Python 3 on that one. > > For this kind of package, I see no

Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

2019-10-13 Thread Thomas Goirand
Hi, In some cases I've seen, particularly in the med or science team, switching some packages to Python 3 requires a significant effort. For example, today I looked into removing Python 2 from python-cogent. Running sixer on all files lead to a huge log of problems to solve by hand. There's no