pyfakefs

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 creates a new empty in-memory file system at each test start, which replaces the real filesystem during the test. Think of pyfakefs as making a per-test temporary directory, except for an entire file system.

pyfakefs is tested with current versions of Linux, Windows and macOS.

Usage

There are several ways to invoke pyfakefs:

using the fs fixture with pytest
deriving from fake_filesystem_unittest.TestCase for unittest
using fake_filesystem_unittest.Patcher as context manager
using the fake_filesystem_unittest.patchfs decorator on a single test

Refer to the usage documentation for more information.

Documentation

Release documentation covers the latest released version
Development documentation for the current main branch
Release Notes
Contributing Guide - contributions are welcome!

Features

Apart from automatically mocking most file-system functions, pyfakefs provides some additional features:

mapping files and directories from the real file system into the fake filesystem
configuration and tracking of the file system size
pause and resume of patching to be able to use the real file system inside a test step
(limited) emulation of other OSes (Linux, macOS or Windows)
configuration to behave as if running as a non-root user while running under root

Limitations

pyfakefs will not work with Python libraries that use C libraries to access the file system. This is because pyfakefs cannot patch the underlying C libraries' file access functions--the C libraries will always access the real file system. Refer to the documentation for more information about the limitations of pyfakefs.

History

pyfakefs.py 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. At last count, pyfakefs was used in over 20,000 Python tests at Google.

Google released pyfakefs to the public in 2011 as a Google Code project. Support for unittest and doctest was added in a fork by user jmcgeheeiv, further corrections were made in a separate fork with user shiffdane, and after the shutdown of Google Code was announced, John McGehee merged all three Google Code projects together here on GitHub. In 2022, the repository has been transferred to pytest-dev to ensure continuous maintenance.

Metadata

Release files for pyfakefs 6.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pyfakefs 6.1.3
File	Size	Uploaded
pyfakefs-6.1.3.tar.gz	226.2 kB	Mar 1, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for pyfakefs 6.1.3
File	Interpreter	ABI	Platform	Reset
pyfakefs-6.1.3-py3-none-any.whl 239.4 kB Mar 1, 2026	Python 3	none	any	Details

Total release size: 465.6 kB

Release files / pyfakefs-6.1.3.tar.gz

Download URL	pyfakefs-6.1.3.tar.gz
Size	226.2 kB
Tags	Source
SHA-256 checksum How to use checksums	`8368ecd2bcdd126362b8900b26dd543afe881d5c396892dcb86e4dc561a39f0f`
BLAKE2b-256 checksum How to use checksums	`6c618faa304523d40299a2e48d69a95a048b06494df92f26a8a9dca06f69899b`
Upload date	Mar 1, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.7`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/pytest-dev/pyfakefs
Publishing commit: github.com/pytest-dev/pyfakefs/tree/45efe81fb93b7f17cd19c82a86976575f22e0e0a

Workflow

Publishing configuration: github.com/pytest-dev/pyfakefs/blob/45efe81fb93b7f17cd19c82a86976575f22e0e0a/.github/workflows/release-deploy.yml
Publishing logs: github.com/pytest-dev/pyfakefs/actions/runs/22539088415/attempts/1

Artifact

Subject: pyfakefs-6.1.3.tar.gz
SHA-256 checksum: 8368ecd2bcdd126362b8900b26dd543afe881d5c396892dcb86e4dc561a39f0f Verifying attestations

Release files / pyfakefs-6.1.3-py3-none-any.whl

Download URL	pyfakefs-6.1.3-py3-none-any.whl
Size	239.4 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`8bf5fa4637ab7749891435c419f155be70fa0341e34b67b0a8a0364cd5e2249d`
BLAKE2b-256 checksum How to use checksums	`8c7c6fc907f6f22a7f0a058c992fcef5ddb11f1b7a9dffe737ddf41a8b9a53e5`
Upload date	Mar 1, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.7`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/pytest-dev/pyfakefs
Publishing commit: github.com/pytest-dev/pyfakefs/tree/45efe81fb93b7f17cd19c82a86976575f22e0e0a

Workflow

Publishing configuration: github.com/pytest-dev/pyfakefs/blob/45efe81fb93b7f17cd19c82a86976575f22e0e0a/.github/workflows/release-deploy.yml
Publishing logs: github.com/pytest-dev/pyfakefs/actions/runs/22539088415/attempts/1

Artifact

Subject: pyfakefs-6.1.3-py3-none-any.whl
SHA-256 checksum: 8bf5fa4637ab7749891435c419f155be70fa0341e34b67b0a8a0364cd5e2249d Verifying attestations