On 25 August 2011 18:00, Éric Araujo <[email protected]> wrote: > Piotr Dobrogost pd at gmane.2011.dobrogost.pl writes: > > Julien Jehannet <julien.jehannet <at> logilab.fr> writes: > >> And of course, we have to stick to the stdlib version with python >= > 3.2. > > Why 3.2 and not 2.7? > > We had the same question for distutils2 last summer. The maintainer of > unittest/unittest2 recommended that we use unittest2 even for 2.7 and > 3.1, where the standard library unittest lacks things that are present > in the 3.2 version. > > To put things in order: > - unittest in 2.7 and 3.1 has lots of improvements > - unittest in 3.2 has even more > - unittest2 == unittest in 3.2 >
Hey Eric, Thanks for answering this. It's not *quite* true. unittest2 *will* equal unittest in python 3.3. The current released version of unittest2 is still equivalent to Python 2.7. I've been very slow in adding all the new features that were in 3.2 and beyond. I'm hoping to do a new release of unittest2 soon. unittest2py3k is a backport of unittest on Python head for Python 3 - so unittest2py3k will include some new unittest features that will be in Python 3.3 but aren't in 3.2. All the best, Michael Foord > > Cheers > _______________________________________________ > Python-Projects mailing list > [email protected] > http://lists.logilab.org/mailman/listinfo/python-projects > -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
