On Sat, 2008-09-27 at 18:57 -0700, Leaf wrote:
[...]
> I'm still a bit confused about the dev process, though - if the code's
> already there, and it won't introduce anything backwards-incompatible,
> why don't they merge it into the trunk? It seems to me that it would
> make development and
On Sep 27, 9:06 pm, Julien Phalip <[EMAIL PROTECTED]> wrote:
> You might want to take a look at ticket #1105. I addresses the issue
> you're raising here, and has been put on the version 1.1 wish-list.
On second thought, I do think that the diff file attached to 1105 does
a better job of this
On Sep 28, 4:20 am, Leaf <[EMAIL PROTECTED]> wrote:
> Out of necessity, I've made a modification to my Django trunk. It
> gives a parameter to the Library.simple_tag() function named
> takes_context.
You might want to take a look at ticket #1105. I addresses the issue
you're raising here, and
Out of necessity, I've made a modification to my Django trunk. It
gives a parameter to the Library.simple_tag() function named
takes_context. This works like the takes_context on
Library.inclusion_tag() - it gives the tag the context. So far, I've
done manual tests on it for:
+ Accepting the
