Re: Removing some python3-* packages
On Thu, Jul 2, 2015 at 10:03 PM, Robert Collins
<robertc@robertcollins.net> wrote:
> On 3 July 2015 at 11:44, Ian Cordasco <graffatcolmingov@gmail.com> wrote:
>> On Thu, Jul 2, 2015 at 6:40 PM, Ben Finney <ben+debian@benfinney.id.au> wrote:
>>> Barry Warsaw <barry@debian.org> writes:
>>>
>>>> […] there's actually no reason to have a Python 3 version of enum in
>>>> any version >= Python 3.4. […]
>>>
>>> Ian Cordasco <graffatcolmingov@gmail.com> writes:
>>>
>>>> Probably a silly question, but are other libraries like unittest2 also
>>>> being packaged for python3? Another library is mock. That was included
>>>> in the stdlib in 3.3.
>>>
>>> One consideration is: What code is written to be Python 2 and Python 3
>>> compatible from the same code base, which achieves this by importing a
>>> module which is backported to Python 2?
>>>
>>> In some of my code I'm doing ‘import unit2’ to have features from that
>>> library available in Python 2 code.
>>>
>>> Since those features are all in Python 3's standard library, the case
>>> could be made that ‘python3-unit2’ is pointless; but against that is the
>>> fact that a Python 3 ‘unit2’ package means that ‘import unit2’ will work
>>> the same on both runtime versions.
>>>
>>> So I'd argue that ‘python3-mock’ and the like do have a place in Debian:
>>> they make it easier to follow the recommended strategy of having a code
>>> base run unchanged on Python2 and Python 3.
>>
>> Just to be clear, trying to use mock on 3.4 is thoroughly broken. If
>> you can install python3-mock right now and use it in 3.4, then y'all
>> must be carrying patches to make it work. The last 3.x version that
>> mock works on is 3.3.
>>
>> That clearly doesn't have a place on a debian with python 3.5 as the
>> version of python 3 included, unless you're planning on supporting
>> packages for python 3.3 as well that will generate a numerous amount
>> of bugs for you.
>
> See my prior mail. I will be backporting all the changes in mock from
> the stdlib to the mock standalone lib in the near future.
>
> I have upload acls from Michael Foord for PyPI and I'm not afraid to
> use them to fix it up - if you wanted to prep a narrow patch to fix
> 3.4 then please do so here - https://github.com/testing-cabal/mock
Will do in the next couple weeks. I had chatted with Michael about it
on Twitter and he expressed no interest in supporting it.
Reply to: