Since you can judge request method in
view, dispatching the same url with different methods to proper views isn't a
problem.
I did similar dispatching in http://mashup.googlecode.com/svn/trunk/mashup/views.py.
- Original Message -
From:
Simon de Haan
To: django-develop
I've attached my patch with the ticket. After patching both of the
following work:
# return a string , as before
@register.simple_tag
def func(...):
...
return 'a string'
# return a dict, items of the dict will be set to context
@register.simple_tag
def func(...):
...
return
Done. Ticket #2619
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EM
simple_tag and inclusion_tag make writing simple template tags much more
convenient.
As the document says, "Another common type of template tag is the type that
displays
some data by rendering another template", e.g.
{% for choice in choices %}
{{ choice }}
{% endfor %}
But if there a
Model reference -> Model methods:
methods ' indent is at the same level of class.
Model reference -> Modifying initial Manager QuerySets:
Model reference -> AutoField
Model reference -> Using models
Model reference -> The field_options dictionary can have the following
keys
"System Mess
