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

[Scott Kitterman]

On Monday, April 20, 2020 8:51:10 AM EDT 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 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?

The Python 2 pypy variant isn't being dropped, so if pypy-funcsigs has 
rdepends, it should probably stay.  In the interest of maintaining momentum on 
the Python 2, I think it would be better to just drop python-funcsigs and sort 
out the future of pypy-funcsigs and python3-funcsigs later.

> > 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.

The current nipype maintainer is well aware of the issue.  AIUI they are 
holding off on uploading to Unstable until they are confident the Python 3 port 
is sufficiently mature.  Since it's already out of Testing and uninstallable in 
Sid, you can ignore causing further breakage (it won't get any more 
uninstallable).

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

I think the original option 2 still makes the most sense.

Scott K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20200420/b0253c43/attachment-0001.sig>