Nope, I mean that the value of 'name 'argument will be the name of the
tag in templates, so tags {% tag_one %} and {% tag_two %} will call
the same function, and render result in different templates.
On 14 янв, 16:29, marco carminati <[email protected]> wrote:
> seehttp://docs.djangoproject.com/en/dev/howto/custom-template-tags/
>
> you should use the 'context' parameter.
>
> from link
> "Sometimes, your inclusion tags might require a large number of
> arguments, making it a pain for template authors to pass in all the
> arguments and remember their order. To solve this, Django provides a
> takes_context option for inclusion tags. If you specify takes_context
> in creating a template tag, the tag will have no required arguments,
> and the underlying Python function will have one argument -- the
> template context as of when the tag was called."
>
> On Jan 14, 3:17 am, SvartalF <[email protected]> wrote:
>
>
>
>
>
>
>
> > Why 'inclusion_tag' from 'django.template' does not accept the
> > argument 'name', as the method of 'tag' does?
>
> > For example, I need two inclusion_tag's with the same functionality
> > but with different templates. It would be nice to do something like
> > this:
>
> > register.inclusion_tag('first.html', name='tag_one')
> > (base_tag_function)
> > register.inclusion_tag('second.html', name='tag_two')
> > (base_tag_function)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
