[Python-modules-team] Bug#938756: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

[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 builds the python2 package but does not run tests with
>> python 2.
> Funcsigs is a backport of the PEP 362 function signature features from
> Python 3.3's inspect module.
Thanks for the info.
> Python 2 has never been removed from this
> package. Though instead, we shall remove this source package entirely
> from Debian.
# Broken Depends:
nipype: python-nipype
pytest: pypy-pytest
python-logfury: python3-logfury
python-oslo.utils: python3-oslo.utils

# Broken Build-Depends:
beaker: python3-funcsigs
kombu: python3-funcsigs
nipype: python-funcsigs
pagure: python3-funcsigs
pytest: pypy-funcsigs
python-oslo.log: python3-funcsigs
python-oslo.utils: python3-funcsigs (>= 0.4)
ripe-atlas-cousteau: python3-funcsigs

If what you say is correct then it sounds like the python3-funcsigs revese depedencies could be dealt with fairly easily.

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? are pypy-* packages only useful with python2 pypy or are they also useful with python3 pypy?

> Traceback2 *already* has Python 2 support removed in Sid. I uploaded
> this on the 21st of march, pressured by its potential autoremoval.

Sorry it seems I got my package names mixed up when writing the list of options. I said traceback2 where I meant unittest2.

> There's no other choice but to fix nipype at this point, or wait until
> it gets autoremoved from Testing.
It already was autoremoved from testing.
>   IMO, it'd be fine to NMU a new
> upstream release if you contact the current maintainer and/or using the
> delayed queue.
A new upstream release for a package I do not use is not something I feel comfortable NMUing. I was hoping that my initial mail would prompt action on the parts of the nipype maintainers but if they don't respond then I tend towards ignoring breakage of sid-only packages that need non-trivial fixes.

> IMO, we should get unittest2 free of Py2 support ASAP, and open an FTP
> team bug to get funcsigs removed from Debian.
>
> Cheers,
>
> Thomas Goirand (zigo)