Hello,
Author: raymond.hettinger Date: Mon Nov 29 02:38:25 2010 New Revision: 86855 Log: Do not add an obsolete unittest name to Py3.2.
Modified: python/branches/py3k/Lib/unittest/case.py
- # Old name for assertCountEqual()
- assertItemsEqual = assertCountEqual
When we merge distutils2 back into the stdlib, our tests will have to work with stdlib unittest in 3.3 or unittest2 for older Pythons (we’ll still make standalone releases for them). unittest2 doesn’t have assertCountEqual, unittest in 3.2+ doesn’t have assertItemsEqual, what’s the plan for compatibility?
Regards
On 09/12/2010 03:45, Éric Araujo wrote:
Hello,
Author: raymond.hettinger Date: Mon Nov 29 02:38:25 2010 New Revision: 86855 Log: Do not add an obsolete unittest name to Py3.2. Modified: python/branches/py3k/Lib/unittest/case.py
- # Old name for assertCountEqual()
- assertItemsEqual = assertCountEqual
When we merge distutils2 back into the stdlib, our tests will have to work with stdlib unittest in 3.3 or unittest2 for older Pythons (we’ll still make standalone releases for them). unittest2 doesn’t have assertCountEqual, unittest in 3.2+ doesn’t have assertItemsEqual, what’s the plan for compatibility?
unittest2 will continue to track changes in unittest. A 0.6.0 release is planned, with feature parity with the version of unittest in Python 3.2. Of course if you want to help that would be much appreciated. :-)
All the best,
Michael Foord
Regards
Le 09/12/2010 11:57, Michael Foord a écrit :
unittest2 will continue to track changes in unittest. A 0.6.0 release is planned, with feature parity with the version of unittest in Python 3.2.
All right. We’ll just run a sed over our tests and bump our required unittest2 version. Thanks for the answer.
Of course if you want to help that would be much appreciated. :-)
I would if I could, but I have my own synchronization to take care of :)
Best regards