Validate template tag context argument at definition time, rather than compile time

[Jake Howard]

If a template tag is defined incorrectly, by not accepting a context argument with takes_context=True:

@register.simple_tag(takes_context=True)
def my_tag():
    pass

An error is only raised when the template is compiled, rather than when the tag is defined as someone may expect. This means there’s extra work done at compile time, which is duplicated each time the tag is used, across multiple templates.

Moving this validation to be done at definition time would likely improve performance. Reading the function signature is already done at definition time, so the performance improvement will likely only be checking the list of arguments, but reporting the error earlier would probably also be a DX improvement.

See also ​forum thread.

[Natalia Bidart]

Thank you Jake! Once the fix is in place, I would like to see some before/after benchmarks for the startup time to confirm the assumption that this won't hurt it.

[Jake Howard]

​PR

As mentioned in the PR description, because the majority of the work was already being done eagerly, the performance benefit is likely to be within margin of error for Python benchmarks (it's just a list member check). Therefore, I've not done any benchmarks currently.

[Jacob Walls <jacobtylerwalls@…>]

In 0ac54863:

Fixed #36728 -- Validated template tag arguments at definition time.

Before, context and content were validated at compile time.