On 8 October 2015 at 11:26, Brian May <br...@microcomaustralia.com.au> wrote: > On Thu, 8 Oct 2015 at 08:18 Robert Collins <robe...@robertcollins.net> > wrote: >> >> Probably the discover improvements in 3.5 try using python -m >> unittest2.discover > > > Just trying that now. > > I see that there is a python3-unittest2 package - should I be using that one > or the unittest built in Python 3.5?
let me check I understood the symptoms: python3.5 - works python2.x fails python3.4 fails So for that - use unittest2 consistently everywhere IMO. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud
