generalov/flexmock — comment on commit 885095c8b8bfaa398039548dccef3dbfd889f461
File:  line 0
By generalov:

Not always. Let's look at https://docs.djangoproject.com/en/1.3/topics/testing/#writing-unit-tests :

> Django ships with a copy of unittest2, a copy of the Python 2.7 unittest library, backported for Python 2.4 compatibility.

> To access this library, Django provides the `django.utils.unittest` module alias. If you are using Python 2.7, or you have installed `unittest2`
> locally, Django will map the alias to the installed version of the unittest library. Otherwise, Django will use it's own bundled version of unittest2.

We are have to use python2.5 . So, monkeypatching hook at `import unittest2` does affect on `django.utils.unittest` only in case of unittest2 module additionally installed, otherwise automatic expectation checking at flexmock has not carried out, because of Django uses a different module instance, really located at django/utils/unittest.