Re: Python < 3.5 tests
On 8 October 2015 at 12:05, Ben Finney <ben+debian@benfinney.id.au> wrote:
> Robert Collins <robertc@robertcollins.net> writes:
>
>> On 8 October 2015 at 11:47, Ben Finney <ben+debian@benfinney.id.au> wrote:
>> > If you have a code base that is intended to run unchanged on Python
>> > 2 and Python 3, and that code base imports ‘unittest2’, you need
>> > both the Python 2 and Python 3 version of that package.
>> >
>> > If your code base targets only Python 3, it should not be using
>> > ‘unittest2’ at all.
>>
>> Thats false. unittest2 is a rolling backport.
>
> I'm not sure how that disagrees with what I wrote.
>
> Are you saying ‘unittest2’ is useful on Python 3.3 (for example) because
> it has improvements from later Python 3 standard library ‘unittest’?
Yes, exactly. unittest2 is useful and relevant on Python 3.2/3.3/3.4
today. Once we get some fixes into 3.6, it will be useful and relevant
for 3.5 users.
> Or something else?
-Rob
--
Robert Collins <rbtcollins@hp.com>
Distinguished Technologist
HP Converged Cloud
Reply to: