forked from orbit-oss/flask
ec0d208bc1
When an exception has been handled when using the request / app context in a with statement, `sys.exc_info()` will still contain the exception information even though it has been handled already. The `__exit__` methods pass in `None` for the exception value in that case, which needs to be distinguisable from the default value for the `exc` parameter. Use a dedicated singleton sentinel value instead. |
||
|---|---|---|
| .. | ||
| ext | ||
| __init__.py | ||
| __main__.py | ||
| _compat.py | ||
| app.py | ||
| blueprints.py | ||
| cli.py | ||
| config.py | ||
| ctx.py | ||
| debughelpers.py | ||
| exthook.py | ||
| globals.py | ||
| helpers.py | ||
| json.py | ||
| logging.py | ||
| sessions.py | ||
| signals.py | ||
| templating.py | ||
| testing.py | ||
| views.py | ||
| wrappers.py | ||