view test/mocknull.py @ 2754:1f89984c0ea5

testJournals: if backend is too fast, two journal entries... ...may come at the same millisecond. as a result, journal is sorted in wrong order and the test fails although functionality being tested is ok. add small delay to work around this - journaled actions rarely occur as frequent in the real life.
author Alexander Smishlajev <a1s@users.sourceforge.net>
date Thu, 14 Oct 2004 10:47:07 +0000
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

Roundup Issue Tracker: http://roundup-tracker.org/