How do I write a null (no-op) contextmanager in Python?

后端 未结 6 821
抹茶落季
抹茶落季 2021-02-01 12:58

Sometimes I need a dummy context manager that does nothing. It can then be used as a stand-in for a more useful, but optional, context manager. For example:

ctx_         


        
相关标签:
6条回答
  • 2021-02-01 13:23

    Since Python 3.2, memoryview(b'') can be use as a no-op context manager. See https://docs.python.org/3/library/stdtypes.html#memoryview.release.

    Pros

    • No imports required

    • Works on 3.2+

    • Roughly twice as fast as contextlib.nullcontext

    Cons

    • You probably want to add a # no-op comment.
    0 讨论(0)
  • 2021-02-01 13:23

    I just used threading.Lock() as a dummy context manager. Temporary lock, only used by the context manager.

    0 讨论(0)
  • 2021-02-01 13:28

    A simple solution for Python 3.6 and below, including 2.7:

    from contextlib import contextmanager
    
    @contextmanager
    def nullcontext(enter_result=None):
        yield enter_result
    

    Since Python 3.7 you should use the provided contextlib.nullcontext instead.

    0 讨论(0)
  • 2021-02-01 13:30

    For Python 2.7+ , you can use

    import contextlib
    with (lambda noop_func: contextlib.contextmanager(noop_func))(lambda: (yield))():
        print("hi")
    
    0 讨论(0)
  • 2021-02-01 13:35

    Python 3.7 and above: use contextlib.nullcontext, specifically designed for this reason.

    Before Python 3.7, the standard library does not offer a context manager specifically designed for these use cases, but there are some workarounds.

    Since Python 3.4, contextlib.suppress can be used for that purpose in the first case, i.e. when there is no as clause:

    ctx_mgr = <meaningfulContextManager> if <condition> else contextlib.suppress()
    
    with ctx_mgr:
        ...
    

    Since Python 3.3, a similar work-around is also available, contextlib.ExitStack, albeit slower than suppress (it takes twice as long in my tests).

    Before Python 3.3, or in case you need an as clause before Python 3.7, developers need to roll their own. Here is one possible implementation (see note at the bottom, but all errors are mine):

    class NullContextManager(object):
        def __init__(self, dummy_resource=None):
            self.dummy_resource = dummy_resource
        def __enter__(self):
            return self.dummy_resource
        def __exit__(self, *args):
            pass
    

    One can then write:

    ctx_mgr = <meaningfulContextManager> if <condition> else NullContextManager(dummy_resource)
    
    with ctx_mgr as resource:
        <operations on resource>
    

    Of course, dummy_resource will need to support all operations required of the "meaningful" resource. So for example, if the meaningful context manager, on __enter__(), returns something that is made to quack() inside the managed block, dummy_resource will also need to support that, albeit possibly without doing anything at all.

    class DummyDuck(object):
        def quack()
            # Ssssh...
            pass
    
    ctx_mgr = <meaningfulContextManager> if <condition> else NullContextManager(DummyDuck())
    
    with ctx_mgr as someDuck:
        someDuck.quack()
    

    Source: A Python feature request. Many thanks to all those who contributed to that discussion. This is my attempt at summarising its outcome in a self-answered question, to save people time reading that long thread. Also see Python documentation's mention of this use of ExitStack.

    0 讨论(0)
  • 2021-02-01 13:35

    Simple solution for Python 2.7, not yet mentioned in the answers:

    from contextlib import nested
    with nested():
        ...
    
    0 讨论(0)
提交回复
热议问题