(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

useful if one wants to access exported template variables from the Python layer: >>> t = Template('{% macro foo() %}42{% endmacro %}23') >>> str(t.module) '23' >>> t.module.foo() == u'42' True This attribute reusable functions to not repeat yourself (“DRY”). Here’s a small example of a macro that renders a form element: 60 {% macro input(name, value='', type='text', size=20) -%} {%- endmacro %} The macro can then be called like a function in the namespace:

{{ input('username') }}

{{ input('password', type='password') }}

If the macro was defined in a different

this mean for you? If you have a macro you want to import, that needs to access the request object you have two possibilities: 1. you explicitly pass the request to the macro as parameter, or the attribute object you are interested in. 2. you import the macro “with context”. Importing with context looks like this: {% from '_helpers.html' import my_macro with context %} Standard Filters Flask provides even nicer, we can write a macro that renders a field with label and a list of errors if there are any. Here’s an example _formhelpers.html template with such a macro: {% macro render_field(field) %}

this mean for you? If you have a macro you want to import, that needs to access the request object you have two possibilities: 1. you explicitly pass the request to the macro as parameter, or the attribute object you are interested in. 2. you import the macro “with context”. Importing with context looks like this: {% from '_helpers.html' import my_macro with context %} 1.6.3 Standard Filters Flask provides even nicer, we can write a macro that renders a field with label and a list of errors if there are any. Here’s an example _formhelpers.html template with such a macro: {% macro render_field(field) %}

{{

Stopping the cluster with ctrl-c or either the SIGTERM and SIGKILL signals, will initiate the Stop procedure: 16:44:12 [Q] INFO Q Cluster-31781 stopping. 16:44:12 [Q] INFO Process-1 stopping cluster processes will halt the pusher and instruct the workers and monitor to finish the remaining items. See Stop procedure Timeouts Before each task execution the worker resets a timer on the sentinel and resets it again Schedule.repeats • Sets the next run time if there are repeats left or if its negative. Stop procedure When a stop signal is given, the sentinel exits the guard loop and instructs the pusher to stop

Stopping the cluster with ctrl-c or either the SIGTERM and SIGKILL signals, will initiate the Stop procedure: 16:44:12 [Q] INFO Q Cluster-31781 stopping. 16:44:12 [Q] INFO Process-1 stopping cluster processes will halt the pusher and instruct the workers and monitor to finish the remaining items. See Stop procedure Timeouts Before each task execution the worker resets a timer on the sentinel and resets it again from Schedule.repeats Sets the next run time if there are repeats left or if its negative. Stop procedure When a stop signal is given, the sentinel exits the guard loop and instructs the pusher to stop

Stopping the cluster with ctrl-c or either the SIGTERM and SIGKILL signals, will initiate the Stop procedure: 16:44:12 [Q] INFO Q Cluster-31781 stopping. 16:44:12 [Q] INFO Process-1 stopping cluster processes will halt the pusher and instruct the workers and monitor to finish the remaining items. See Stop procedure Timeouts Before each task execution the worker resets a timer on the sentinel and resets it again django_q.Schedule.repeats Sets the next run time if there are repeats left or if its negative. Stop procedure When a stop signal is given, the sentinel exits the guard loop and instructs the pusher to stop