> Of course, that's when you break out and write your own view.
Noted. And I shouldn't complain...it's not like they're exactly hard!
> You shouldn't have to import anything inside a template or generic view
> that either don't already have access to. Also, the "free" access
> didn't affect templates to begin with, it was something that model
> classes got.
That's what I thought...I was just flailing about, really. I remembered
the discussion about removing the "free" access, and just decided to
make a command decision and blame that. No need to think I was doing
something WRONG, or anything! *grin*
> It sounds like somewhere below you are trying to do {{
> month.month }} Keep in mind to iterate the months you need something like:
> {% for month in date_list %}
> {{ month|date:"F" }}
> {% endfor %}
> The date filter being the only way to get information from a date time.
Max, you rock. I haven't even tried the code yet and I'm sure it's
correct. I was indeed doing a month.month (or something like that,
don't remember exactly). Can't wait to get back and play with
that...thanks VERY much. It's really just a matter of learning the
Django way. And the great thing is how intuitive the patterns here are.
Thanks again.
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
