Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-30 Thread Moritz Mühlenhoff
On Mon, Apr 20, 2020 at 09:57:30AM +0200, Thomas Goirand wrote: > On 4/20/20 4:36 AM, peter green wrote: > > Funcsigs is a backport of the PEP 362 function signature features from > Python 3.3's inspect module. Python 2 has never been removed from this > package. Though instead, we shall remove

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-25 Thread peter green
On 21/04/2020 22:20, Thomas Goirand wrote: So, if I'm following correctly, what you seem to propose, is to remove Python 2 from unittest2. If that's the case, then I agree with such a plan. I just didn't dare to do it yet. Yes, whichever approach is taken to dealing with funcsigs, unittest2

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-21 Thread Valentin Vidić
On Tue, Apr 21, 2020 at 11:20:16PM +0200, Thomas Goirand wrote: > You can remove all of the python-oslo* from the list. The versions in > Experimental, which are the next version of OpenStack, are fixed. In 2 > weeks of time, I'll upload all what I staged in Experimental to Sid > (maybe 150

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-21 Thread stefanor
Hi Thomas (2020.04.21_21:20:16_+) > > But that still leaves the question of what to do about the dependency of > > pytest on pypy-funcsigs ? should pypy modules be removed from pytest and > > it's reverse-dependencies in the same way that regular python2 modules > > were? how feasible is that?

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-21 Thread Thomas Goirand
On 4/20/20 2:51 PM, peter green wrote: > On 20/04/2020 08:57, Thomas Goirand wrote: >>> Option 1: fix all four packages to be python 2 free. >>> >>> Option 2: Remove python2 stuff from traceback2, python-funcsigs and >>> numba. Break the dependencies of nipype in sid. >>> >>> Option 3: Remove

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-20 Thread peter green
On 20/04/2020 08:57, Thomas Goirand wrote: Option 1: fix all four packages to be python 2 free. Option 2: Remove python2 stuff from traceback2, python-funcsigs and numba. Break the dependencies of nipype in sid. Option 3: Remove python2 stuff from traceback2, modify python-funcsigs so it still

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-20 Thread Thomas Goirand
On 4/20/20 4:36 AM, peter green wrote: > (using -quiet aliases where multiple involved packages have the same > maintainer listed. > > Hi > > I have just been running some self-contained buildability tests on > bullseye and these tests indicated that the python-linecache2 and > python-traceback2