Home
last modified time | relevance | path

Searched refs:modules_to_patch (Results 1 – 4 of 4) sorted by relevance

/external/python/pyfakefs/pyfakefs/
Dfake_filesystem_unittest.py88 modules_to_patch=None, argument
110 modules_to_patch=modules_to_patch,
131 modules_to_patch=None, argument
143 modules_to_patch=modules_to_patch,
195 modules_to_patch = None variable in TestCaseMixin
204 modules_to_patch=None, argument
221 if modules_to_patch is None:
222 modules_to_patch = self.modules_to_patch
226 modules_to_patch=modules_to_patch,
261 modules_to_patch=None, argument
[all …]
/external/python/pyfakefs/docs/
Dusage.rst266 modules_to_patch section in Customizing Patcher and TestCase
270 ``modules_to_patch`` can be used by adding a fake module implementation for
304 with Patcher(modules_to_patch={'django.core.files.locks': FakeLocks}):
310 self.setUpPyfakefs(modules_to_patch={'django.core.files.locks': FakeLocks})
322 @patchfs(modules_to_patch={'django.core.files.locks': FakeLocks})
589 functions or classes, they may be patched by using the ``modules_to_patch``
/external/python/pyfakefs/pyfakefs/tests/
Dfake_filesystem_unittest_test.py320 modules_to_patch={
343 @patchfs(modules_to_patch={
/external/python/pyfakefs/
DCHANGES.md227 * fixed using `modules_to_patch` (regression, see [#450](../../issues/450))
348 * Added possibility to add own fake modules via `modules_to_patch`