functions can find the relevant lock to change when // they are called. This way we avoid global variables. locks.user = mutex; locks.lock = lock_mutex; locks.unlock = unlock_mutex; // This is the main exception. } Since the fz_try macro is based on setjmp, the same conditions that apply to local variables in the presence of setjmp apply. Any locals written to inside the try block may be restored to their 6) 218 Chapter 8. Language Bindings MuPDF Documentation, Release 1.25.0 8.2.7 Runtime environmental variables All builds • MUPDF_mt_ctx Controls support for multi-threading on startup. – If set with

functions can find the relevant lock to change when // they are called. This way we avoid global variables. locks.user = mutex; locks.lock = lock_mutex; locks.unlock = unlock_mutex; // This is the main exception. } Since the fz_try macro is based on setjmp, the same conditions that apply to local variables in the presence of setjmp apply. Any locals written to inside the try block may be restored to their y1=1215.6) 7.1. The C++ MuPDF API 203 MuPDF Documentation, Release 1.24.0 7.1.7 Runtime environmental variables All builds • MUPDF_mt_ctx Controls support for multi-threading on startup. – If set with

functions can find the relevant lock to change when // they are called. This way we avoid global variables. locks.user = mutex; locks.lock = lock_mutex; locks.unlock = unlock_mutex; // This is the main exception. } Since the fz_try macro is based on setjmp, the same conditions that apply to local variables in the presence of setjmp apply. Any locals written to inside the try block may be restored to their const; These each generate text such as: (x0=90.51 y0=160.65 x1=501.39 y1=1215.6) 5.1.6 Environmental variables All builds • MUPDF_mt_ctx Controls support for multi-threading on startup. – If set with

functions can find the relevant lock to change when // they are called. This way we avoid global variables. locks.user = mutex; locks.lock = lock_mutex; locks.unlock = unlock_mutex; // This is the main exception. } Since the fz_try macro is based on setjmp, the same conditions that apply to local variables in the presence of setjmp apply. Any locals written to inside the try block may be restored to their const; These each generate text such as: (x0=90.51 y0=160.65 x1=501.39 y1=1215.6) 7.1.6 Environmental variables All builds • MUPDF_mt_ctx Controls support for multi-threading on startup. – If set with

installed: • On Windows: – Install Visual Studio 2019. If not installed in a standard location, set environmental variable PYMUPDF_SETUP_DEVENV to the location of the devenv.com binary. – Having other installed com:/home/git/mupdf.git • Build PyMuPDF, specifying the location of the local MuPDF tree with the environmental variables PYMUPDF_SETUP_MUPDF_BUILD: cd PyMuPDF && PYMUPDF_SETUP_MUPDF_BUILD=../mupdf pip install PyMuPDF/tests 4.7.1 Notes about using a non-default MuPDF Using a non-default build of MuPDF by setting environmental variable PYMUPDF_SETUP_MUPDF_BUILD can cause various things to go wrong and so is not generally

94 Chapter 5. Changelog Jupyter Notebook Documentation, Release 6.5.1 • Changed all python variables named file to file_name to not override built_in file (2830). • Add more doc tests (2823). • Typos will be passed to Jinja environment. NotebookApp.jinja_template_vars [Dict] Default: {} Extra variables to supply to jinja templates when rendering. NotebookApp.kernel_manager_class [Type] Default: value must also be set on the Gateway server - since that configuration value indicates which environmental values to make available to the kernel. (JUPYTER_GATEWAY_ENV_WHITELIST env var) GatewayClient

2 (2849). 5.45. 5.2.1 93 Jupyter Notebook Documentation, Release 6.5.0 • Changed all python variables named file to file_name to not override built_in file (2830). • Add more doc tests (2823). • Typos will be passed to Jinja environment. NotebookApp.jinja_template_vars [Dict] Default: {} Extra variables to supply to jinja templates when rendering. NotebookApp.kernel_manager_class [Type] Default: value must also be set on the Gateway server - since that configuration value indicates which environmental values to make available to the kernel. (JUPYTER_GATEWAY_ENV_WHITELIST env var) GatewayClient

2 (2849). 5.39. 5.2.1 91 Jupyter Notebook Documentation, Release 6.4.10 • Changed all python variables named file to file_name to not override built_in file (2830). • Add more doc tests (2823). • Typos will be passed to Jinja environment. NotebookApp.jinja_template_vars [Dict] Default: {} Extra variables to supply to jinja templates when rendering. NotebookApp.kernel_manager_class [Type] Default: 'notebook value must also be set on the Gateway server - since that configuration value indicates which environmental values to make available to the kernel. (JUPYTER_GATEWAY_ENV_WHITELIST env var) GatewayClient

92 Chapter 5. Changelog Jupyter Notebook Documentation, Release 6.4.11 • Changed all python variables named file to file_name to not override built_in file (2830). • Add more doc tests (2823). • Typos will be passed to Jinja environment. NotebookApp.jinja_template_vars [Dict] Default: {} Extra variables to supply to jinja templates when rendering. NotebookApp.kernel_manager_class [Type] Default: 'notebook value must also be set on the Gateway server - since that configuration value indicates which environmental values to make available to the kernel. (JUPYTER_GATEWAY_ENV_WHITELIST env var) GatewayClient

2 (2849). 5.39. 5.2.1 91 Jupyter Notebook Documentation, Release 6.4.9 • Changed all python variables named file to file_name to not override built_in file (2830). • Add more doc tests (2823). • Typos will be passed to Jinja environment. NotebookApp.jinja_template_vars [Dict] Default: {} Extra variables to supply to jinja templates when rendering. NotebookApp.kernel_manager_class [Type] Default: 'notebook value must also be set on the Gateway server - since that configuration value indicates which environmental values to make available to the kernel. (JUPYTER_GATEWAY_ENV_WHITELIST env var) GatewayClient