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 will
On 4/22/20 6:23 AM, Valentin Vidić wrote:
> 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 sta
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 package
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?
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 pytho
5 matches
Mail list logo