GitLocker: The Coding Marketplace

Description:

exceptionescaping 0.0.9

If you've just confessed and you can't wait to sin again, try this package. It will help you hide your mistakes and make your life more carefree.
Table of contents

Quick start
Decorator mode
Context manager mode
Logging

Quick start
Install it:
pip install exception_escaping

And use:
import escape

@escape
def function():
raise ValueError

function() # The exception is suppressed.

Read about other library features below.
Decorator mode
The @escape decorator suppresses exceptions in a wrapped function (including a coroutine one), which are passed in parentheses. In this way, you can pass any number of exceptions, for example:
import asyncio
import escape

@escape(ValueError, ZeroDivisionError)
def function():
raise ValueError('oh!')

@escape(ValueError, ZeroDivisionError)
async def async_function():
raise ZeroDivisionError('oh!')

function() # Silence.
asyncio.run(async_function()) # Silence.

If you use @escape with parentheses but do not pass any exception types, no exceptions will be suppressed:
@escape()
def function():
raise ValueError('oh!')

function()
# > ValueError: oh!

If an exception occurred inside the function wrapped by the decorator, it will return the default value - None. You can specify your own default value:
@escape(ValueError, default='some value')
def function():
raise ValueError

assert function() == 'some value' # It's going to work.

Finally, you can use @escape as a decorator without parentheses.
@escape
def function():
raise ValueError

function() # Silence still.

In this mode, not all exceptions from the hierarchy are suppressed, but only those that can be expected in the user code. Exception and all its descendants are suppressed, as well as, starting with Python 3.11, groups of exceptions. However, exceptions GeneratorExit, KeyboardInterrupt and SystemExit are not escaped in this mode. This is due to the fact that in most programs none of them is part of the semantics of the program, but is used exclusively for system needs. For example, if KeyboardInterrupt was blocked, you would not be able to stop your program using the Control-C keyboard shortcut.
You can also use the same set of exceptions in parenthesis mode as without parentheses. To do this, use the Ellipsis (three dots):
@escape(...)
def function_1():
raise ValueError

@escape
def function_2():
raise ValueError

function_1() # These two functions are completely equivalent.
function_2() # These two functions are completely equivalent.

Ellipsis can also be used in enumeration, along with other exceptions:
@escape(GeneratorExit, ...)

Context manager mode
You can use escape as a context manager, which escapes exceptions in the code block wrapped by it. You can call it according to the same rules as the decorator - pass exceptions or ellipsis there. It also works almost the same way as contextlib.suppress from the standard library, but with a bit more opportunities. Some examples:
with escape(ValueError):
raise ValueError

with escape:
raise ValueError

with escape(...):
raise ValueError

However, as you should understand, the default value cannot be specified in this case. If you try to specify a default value for the context manager, get ready to face an exception:
with escape(default='some value'):
...

# > escape.errors.SetDefaultReturnValueForContextManagerError: You cannot set a default value for the context manager. This is only possible for the decorator.

Logging
You can pass a logger object to the escape. In such case, if an exception is raised inside the context or the function wrapped by the decorator, it will be logged:
import logging
import escape

logging.basicConfig(
level=logging.INFO,
format="%(asctime)s [%(levelname)s] %(message)s",
handlers=[
logging.StreamHandler(),
]
)

logger = logging.getLogger('logger_name')

with escape(..., logger=logger):
1/0

# You will see a description of the error in the console.

It works in any mode: both in the case of the context manager and the decorator.
Only exceptions are logged. If the code block or function was executed without errors, the log will not be recorded. Also the log is recorded regardless of whether the exception was suppressed or not. However, depending on this, you will see different log messages to distinguish one situation from another.