Noticed this when Maru Newby asked me about the non-failing import
errors in Neutron - which lead eventually to
https://review.openstack.org/#/c/171874/.

Neutron was using 'unittest', but we depend on the fixes in cPython
3.5, which are backported in unittest2. We should not use 'unittest'
itself anywhere in OpenStack, only 'unittest2'.

testtools has a hard dependency on unittest2 these days (as we port
features from it into cPython's unittest, they come back as backports
in unittest2), so there's no dependency-chain reason to avoid using
unittest2.

Cheers,
Rob

-- 
Robert Collins <[email protected]>
Distinguished Technologist
HP Converged Cloud

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to