From 61b45dff6be3a2c85adac73acf5fe0de71f9ecda Mon Sep 17 00:00:00 2001 From: Baptiste Mispelon Date: Fri, 26 Aug 2016 11:39:06 +0200 Subject: Fixed #27126 -- Made {% regroup %} return a namedtuple to ease unpacking. --- docs/ref/templates/builtins.txt | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) (limited to 'docs/ref') diff --git a/docs/ref/templates/builtins.txt b/docs/ref/templates/builtins.txt index 1a8fe600ac..9a5bd4abba 100644 --- a/docs/ref/templates/builtins.txt +++ b/docs/ref/templates/builtins.txt @@ -896,13 +896,36 @@ resulting list. Here, we're regrouping the ``cities`` list by the ``country`` attribute and calling the result ``country_list``. ``{% regroup %}`` produces a list (in this case, ``country_list``) of -**group objects**. Each group object has two attributes: +**group objects**. Group objects are instances of +:py:func:`~collections.namedtuple` with two fields: * ``grouper`` -- the item that was grouped by (e.g., the string "India" or "Japan"). * ``list`` -- a list of all items in this group (e.g., a list of all cities with country='India'). +.. versionchanged:: 1.11 + + The group object was changed from a dictionary to a + :py:func:`~collections.namedtuple`. + +Because ``{% regroup %}`` produces :py:func:`~collections.namedtuple` objects, +you can also write the previous example as:: + + {% regroup cities by country as country_list %} + + + Note that ``{% regroup %}`` does not order its input! Our example relies on the fact that the ``cities`` list was ordered by ``country`` in the first place. If the ``cities`` list did *not* order its members by ``country``, the -- cgit v1.3