Introduction¶
pyfakefs implements a fake file system that mocks the Python file system modules. Using pyfakefs, your tests operate on a fake file system in memory without touching the real disk. The software under test requires no modification to work with pyfakefs.
pyfakefs
works with CPython 3.7 and above, on Linux, Windows and macOS,
and with PyPy3.
pyfakefs
works with pytest version 6.2.5 or above by
providing the fs fixture that enables the fake filesystem.
Installation¶
pyfakefs
is available on PyPI.
The latest released version can be installed from PyPI:
pip install pyfakefs
The latest development version (main branch) can be installed from the GitHub sources:
pip install git+https://github.com/pytest-dev/pyfakefs
Features¶
Code executed under
pyfakefs
works transparently on a memory-based file system without the need of special commands. The same code that works on the real filesystem will work on the fake filesystem if running underpyfakefs
.pyfakefs
provides direct support for pytest (see Patch using the pytest plugin) and unittest (see Patch using fake_filesystem_unittest), but can also be used with other test frameworks.Each
pyfakefs
test starts with an empty (except for the OS temporary directories) file system, but it is possible to map files and directories from the real file system into the fake filesystem if needed (see Access to files in the real file system).No files in the real file system are changed during the tests, even in the case of writing to mapped real files.
pyfakefs
keeps track of the filesystem size if configured. The file system size can be configured arbitrarily (see Setting the file system size). It is also possible to create files with a defined size without setting contents.It is possible to pause and resume using the fake filesystem, if the real file system has to be used in a test step (see Suspending patching).
pyfakefs
defaults to the OS it is running on, but can also be configured to test code running under another OS (Linux, macOS or Windows, see Simulating other file systems).pyfakefs
can be configured to behave as if running as a root or as a non-root user, independently from the actual user (see allow_root_user).
Limitations¶
pyfakefs
will not work with Python libraries (other than os and io) that use C libraries to access the file system, because it cannot patch the underlying C libraries’ file access functionspyfakefs
patches most kinds of importing file system modules automatically, but there are still some cases where this will not work. See Customizing patching for more information and ways to work around this.pyfakefs
does not retain the MRO for file objects, so you cannot rely on checks using isinstance for these objects (for example, to differentiate between binary and textual file objects).pyfakefs
is only tested with CPython and the newest PyPy versions, other Python implementations will probably not workDifferences in the behavior in different Linux distributions or different macOS or Windows versions may not be reflected in the implementation, as well as some OS-specific low-level file system behavior. The systems used for automatic tests in GitHub Actions are considered as reference systems. Additionally, the tests are run in Docker containers with the latest CentOS, Debian, Fedora and Ubuntu images.
pyfakefs
may not work correctly if file system functions are patched by other means (e.g. using unittest.mock.patch) - see Pyfakefs and mock_open for more informationpyfakefs
will not work correctly with behave due to the way it loads the steps, if any filesystem modules are imported globally in the steps or environment files; as a workaround, you may load them locally inside the test steps (see this issue)pyfakefs
is not guaranteed to work correctly in multi-threading environments. Specifically, it does not ensure concurrent write access to a file from different threads, which is possible under Posix.
History¶
pyfakefs
was initially developed at Google by
Mike Bland as a modest
fake implementation of core Python modules. It was introduced to all of
Google in September 2006. Since then, it has been enhanced to extend its
functionality and usefulness. At last count, pyfakefs
was used in over
20,000 Python tests at Google.
Google released pyfakefs
to the public in 2011 as Google Code project
pyfakefs:
Fork jmcgeheeiv-pyfakefs added direct support for unittest and doctest as described in Patch file system with unittest and doctest
Fork shiffdane-jmcgeheeiv-pyfakefs added further corrections
After the shutdown of Google Code was announced, John McGehee merged all three Google Code projects together on GitHub where an enthusiastic community actively maintains and extends pyfakefs. In 2022, the repository has been transferred to pytest-dev to ensure continuous maintenance.