Make sure you have checked all steps below.

Jira

• My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"
  • https://issues.apache.org/jira/browse/AIRFLOW-4451
  • In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
  • In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

• Here are some details about my PR, including screenshots of any UI changes:

PR #4691 introduced an issue where named tuples were inadvertently converted to a list of rendered entities. This then made subsequent attribute access on what was assumed to be a named tuple fail, since the object was actually a list.

Example:

from collections import namedtuple

Test = namedtuple('Test', ['foo', 'bar'])
t = Test(1, 2)

t = render_template(t)  # `t` is now a list of [1, 2]
print(t.foo)  # This fails after rendering

This PR adds an additional clause in the base render function to catch named tuples, and re-instantiate them as the proper class after variable rendering.

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:
  This adds another clause to the python operator tests to ensure that rendered op_args that are named tuples are still preserved.

Commits

• My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does
  • If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

Code Quality

• Passes flake8