| commit | b9bac58153d40c24d4c4dbd5014ef7f6e6870d9d | [log] [tgz] |
|---|---|---|
| author | Simon Ruggier <simon@platform.sh> | Thu Apr 07 15:41:31 2016 -0400 |
| committer | Simon Ruggier <simon@platform.sh> | Thu Apr 28 17:04:23 2016 -0400 |
| tree | a95c025d522eb49532d7f3eb1525ae0532191b04 | |
| parent | 3fc3ad1d4e347af594f93bf5fcd3be91396735c4 [diff] |
Implement hard link support This change adds support for hard links, and tests to go along with that. There is a bit of ugliness in this change around the use of the name field on FakeFile instances. Support for hard links means that the same file can have different names under different directories, so it fundamentally doesn't make sense for FakeFile instances to have a name associated with them. However, I didn't want to have to perform a mass refactoring as a prerequisite to making this change, so it instead just sets the filename as needed to work with the existing implementation of AddObject. This has the unavoidable side effect of changing the name associated with the original file as well, since they share the same FakeFile instance. It looks like this is probably safe to do now, but to properly ensure that there aren't any problems related to this, the whole codebase should be refactored to remove the name field from FakeFile, and replace it with a suitable alternative. It may require a wrapper class that helps callers keep track of a file's name while preventing misuse of that information by direct users of FakeFile.
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.
See the usage tutorial for a concrete example of how to apply pyfakefs.
Usually you would use it this way:
import pyfakefs.fake_filesystem as fake_fs # Create a faked file system fs = fake_fs.FakeFilesystem() # Do some setup on the faked file system fs.CreateFile('/var/data/xx1.txt') fs.CreateFile('/var/data/xx2.txt') # Replace some built-in file system related modules you use with faked ones # Assuming you are using the mock library to ... mock things try: from unittest.mock import patch # In Python 3, mock is built-in except ImportError: from mock import patch # Python 2 import pyfakefs.fake_filesystem_glob as fake_glob # Note that this fake module is based on the fake fs you just created glob = fake_glob.FakeGlobModule(fs) with patch('mymodule.glob', glob): print(glob.glob('/var/data/xx*'))
pyfakefs is automatically tested with Python 2.6 and above, and it is currently 
.
See Travis-CI for test results for each Python version.
pyfakefs works with Python 2.6 and above. pyfakefs requires mox3.
pyfakefs is available on PyPi.
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. Since then, it has been enhanced to extend its functionality and usefulness. At Google alone, pyfakefs is used in over 2,000 Python tests.
Google released pyfakefs to the public in 2011 as Google Code project pyfakefs.
Fork jmcgeheeiv-pyfakefs added a usage tutorial, direct support for 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 here on GitHub where an enthusiastic community actively maintains and extends pyfakefs.