(using fz_throw, or fz_rethrow). } The fz_always block is optional, and can safely be omitted. The macro based nature of this system has 3 main limitations: Never return from within try (or ‘goto’ or longjmp process of throwing that excep- tion. As a way of mitigating this problem, we provide a fz_var() macro that tells the compiler to ensure that that variable is not unset by the act of throwing the exception fz_catch(ctx) { // This block is only executed when recovering from an exception. } Since the fz_try macro is based on setjmp, the same conditions that apply to local variables in the presence of setjmp apply

(using fz_throw, or fz_rethrow). } The fz_always block is optional, and can safely be omitted. The macro based nature of this system has 3 main limitations: Never return from within try (or ‘goto’ or longjmp process of throwing that excep- tion. As a way of mitigating this problem, we provide a fz_var() macro that tells the compiler to ensure that that variable is not unset by the act of throwing the exception fz_catch(ctx) { // This block is only executed when recovering from an exception. } Since the fz_try macro is based on setjmp, the same conditions that apply to local variables in the presence of setjmp apply

(using fz_throw, or fz_rethrow). } The fz_always block is optional, and can safely be omitted. The macro based nature of this system has 3 main limitations: Never return from within try (or ‘goto’ or longjmp process of throwing that excep- tion. As a way of mitigating this problem, we provide a fz_var() macro that tells the compiler to ensure that that variable is not unset by the act of throwing the exception fz_catch(ctx) { // This block is only executed when recovering from an exception. } Since the fz_try macro is based on setjmp, the same conditions that apply to local variables in the presence of setjmp apply

(using fz_throw, or fz_rethrow). } The fz_always block is optional, and can safely be omitted. The macro based nature of this system has 3 main limitations: Never return from within try (or ‘goto’ or longjmp process of throwing that excep- tion. As a way of mitigating this problem, we provide a fz_var() macro that tells the compiler to ensure that that variable is not unset by the act of throwing the exception fz_catch(ctx) { // This block is only executed when recovering from an exception. } Since the fz_try macro is based on setjmp, the same conditions that apply to local variables in the presence of setjmp apply

and then compiling it on your machine. 2. Installation of PyMuPDF: this step is normal Python procedure. Usually you will have to adapt the setup.py to point to correct include and lib directories of

encountered via xref can be processed as it is. To recover the original image using PyMuPDF, the procedure depicted as follows must be executed: >>> pix1 = fitz.Pixmap(doc.extract_image(xref)["image"])