What is the advantage in using a context? You only put the content i would
put directly into the render_to_response arguments in an own dict, like
context = {'foo':'bar'}
return context
is equal to
return {'foo':'bar'}
???
But thanks to your code -- it's much better than mine ;-)
--
You rec
Thank you very much!! I know my code needs to be tidied up xD. I'vd tried many
things to solve the problem that's why my code looks so awful. And I'm glad
there is an easy solution for my problem (and I didn't saw it *wall*)
And @bruno desthuilliers: It's good for a newbie like me to see how ot
On 08/14/2011 09:57 PM, bruno desthuilliers wrote:
{% for current, entry, month, n in months %}
Please think about what "months" is here... Yes, a list of dicts. So
this line is the equivalent of:
current = months[0] # first dict in the list
entry = months[1]# second dict in the list
month
Hi,
your template is missing a closing double-quote
this line
> "month{% endif %} >
should be
> "month"{% endif %} >
Also by reformatting a little I noticed you close a with a
{% for current, entry, month, n in months %}
{% if entry %}{% endif %}
http://foo.bar/"
On 14 août, 20:11, Schmidtchen Schleicher
wrote:
> Hey Guys,
> my problem is, as shown in the subject, that the template-engine puts in the
> name of the templatevariable instead of the value:
>
> my view:
>
> def YearlyView(request, calid, year):
The convention is to use all_lower names for func
Hey Guys,
my problem is, as shown in the subject, that the template-engine puts in the
name of the templatevariable instead of the value:
my view:
def YearlyView(request, calid, year):
lst = []
k = get_object_or_404(Kalender, pk=calid)
now_year, now_month = datetime.date.today().year
6 matches
Mail list logo