Mercurial > p > roundup > code
view test/mocknull.py @ 5317:c0cda00af479
Fix tests for memorydb and anydbm backends
The anydbm backend silently drops properties in the journal that are not
in the database during serialisation. The memorydb backend (only used
for testing) cannot deal with user changes (re-open of db under a
different user).
| author | Ralf Schlatterbeck <rsc@runtux.com> |
|---|---|
| date | Thu, 19 Apr 2018 17:03:11 +0200 |
| parents | 79fd8537ae3b |
| children | 3757449e00c4 |
line wrap: on
line source
class MockNull: def __init__(self, **kwargs): for key, value in kwargs.items(): self.__dict__[key] = value def __call__(self, *args, **kwargs): return MockNull() def __getattr__(self, name): # This allows assignments which assume all intermediate steps are Null # objects if they don't exist yet. # # For example (with just 'client' defined): # # client.db.config.TRACKER_WEB = 'BASE/' self.__dict__[name] = MockNull() return getattr(self, name) def __getitem__(self, key): return self def __nonzero__(self): return 0 def __str__(self): return '' def __repr__(self): return '<MockNull 0x%x>'%id(self) def gettext(self, str): return str _ = gettext
