Let the template parser remember it's root nodelist

[Chris Beaven]

This is useful if tags want to parse the templates root nodelist (built up to the current parsing point) for some reason.

As a specific example, I've got a {% repeatblock %} tag (which duplicates the nodelist of an existing block) which needs this functionality.

[Jacob]

I don't quite understand what this does -- can you give me more details about why this is important?

[Chris Beaven]

Sure. The problem I was facing is that my tag needed to find a separate node (generated by previously parsed tokens).

Currently, the parser creates a root nodelist when starts parsing the tokens (nodelist = self.create_nodelist()) but there is no way to access this nodelist because it is only a local variable.
By allowing this to be an instance variable it allows tags (which accept the parser instance as one of the arguments) to inspect - and modify if necessary - the nodelist created so far.

Specifically, my {% repeatblock %} tag was taking on the suggestion of Malcolm regarding allowing a the contents of a block node to be used more than once in an old discussion (which, in certain cases, would still be useful)

[Chris Beaven]

I couldn't find my old tag, so I remade it and put it here for an example: ​http://github.com/SmileyChris/django-repeatblock

[belgabor]

Unfortunately this falls apart if the block and repeatblock tag occur in the same block-level tag (eg autoescape). I'm not sure if there is an easy fix :/

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[anonymous]

Actually if the reason behind such a change is just the repeatblock tag, I believe it's quite unnecessary as there is a solution for this particular problem -- goo.gl/caOOu

[Chris Beaven]

It's not the reason, that was just an example of the usefulness of such a pointer.

But it's not something I've heard any requests for, and since I opened it, I'll close it.