[checkmk-commits] [tribe29/checkmk] 40686d: Make our globals more Flask-like.

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 40686d8bcc0b89e66714d4e179b8afc09a567e77 https://github.com/tribe29/checkmk/commit/40686d8bcc0b89e66714d4e179b8afc09… Author: Sven Panne <sven.panne(a)tribe29.com> Date: 2019-08-07 (Wed, 07 Aug 2019) Changed paths: M cmk/gui/bi.py M cmk/gui/globals.py M cmk/gui/gui_background_job.py M cmk/gui/inventory.py M cmk/gui/log.py M cmk/gui/modules.py M cmk/gui/plugins/metrics/utils.py M cmk/gui/plugins/views/icons/builtin.py M cmk/gui/plugins/views/inventory.py M cmk/gui/plugins/views/painters.py M cmk/gui/plugins/views/utils.py M cmk/gui/plugins/wato/builtin_attributes.py M cmk/gui/plugins/wato/utils/__init__.py M cmk/gui/userdb.py M cmk/gui/utils.py M cmk/gui/watolib/git.py M cmk/gui/watolib/hosts_and_folders.py M cmk/gui/watolib/sidebar_reload.py M cmk/update_config.py M tests/unit/cmk/gui/conftest.py M web/app/index.wsgi Log Message: ----------- Make our globals more Flask-like. * Use LocalProxy from werkzeug instead of our own class, just like Flask. * Explicitly introduce application/request contexts. Although we don't really make a distinction between those two kinds, it is the right thing to do when we want to move to Flask some day. * Push/pop the contexts via context managers instead of fragile and bug-prone set/unset calls. * Move the global "g" to the application context where it belongs. * Remove a few no-op comments on the way. Change-Id: I5baa1aca2a18e2e584480f3422c9a6783c6ed0fb