forked from orbit-oss/flask
commit
ea73571a54
3 changed files with 3 additions and 3 deletions
|
|
@ -53,7 +53,7 @@ every time the app context tears down. So what does this mean?
|
|||
Essentially the app context is created before the request comes in and is
|
||||
destroyed (teared down) whenever the request finishes. A teardown can
|
||||
happen because of two reasons: either everything went well (the error
|
||||
parameter will be `None`) or an exception happend in which case the error
|
||||
parameter will be `None`) or an exception happened in which case the error
|
||||
is passed to the teardown function.
|
||||
|
||||
Curious about what these contexts mean? Have a look at the
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ def with_metaclass(meta, *bases):
|
|||
# breaks the __exit__ function in a very peculiar way. This is currently
|
||||
# true for pypy 2.2.1 for instance. The second level of exception blocks
|
||||
# is necessary because pypy seems to forget to check if an exception
|
||||
# happend until the next bytecode instruction?
|
||||
# happened until the next bytecode instruction?
|
||||
BROKEN_PYPY_CTXMGR_EXIT = False
|
||||
if hasattr(sys, 'pypy_version_info'):
|
||||
class _Mgr(object):
|
||||
|
|
|
|||
|
|
@ -662,7 +662,7 @@ def get_root_path(import_name):
|
|||
'module came from an import hook that does '
|
||||
'not provide file name information or because '
|
||||
'it\'s a namespace package. In this case '
|
||||
'the root path needs to be explictly '
|
||||
'the root path needs to be explicitly '
|
||||
'provided.' % import_name)
|
||||
|
||||
# filepath is import_name.py for a module, or __init__.py for a package.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue