On Jun 5, 7:02 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Hrm, this does not occur for me even after I remove all .pyc files
> from the django dir.
Are you sure you're importing both Template and Context? I get the
same error as OP.
Trevor
--~--~-~--~~~---~--
es that can support the
> optimization.
Would it be possible to, instead of manually specifying when to reset
the database, automatically reset the database the first time that a
test attempts to access it in a test case, and not reset again until
the next test case after one which modifies it
> Changing the name would just give folks another thing to ignore.
If the name of the list were changed to, say, "django-internal", you
would have to ignore the name of the list to accidentally mis-post;
this is very unlikely, and hardly "another thing to ignore". Right
now, all that you'd have to
On Apr 8, 12:14 pm, AmanKow <[EMAIL PROTECTED]> wrote:
> I don't know about sticking that in core, but that sure is a neat idea
> that I think I might use in some personal stuff. Particularly useful
> when urls have a complex 'bases' that I wish to use to parse the same
> info out of groups of ur
Since assignment of variables is illegal in the template syntax, and
{% blocktrans %} cannot contain other tags (notably {% url %}), there
is a problem for marking strings as translatable which contain links
in them in django templates.
Sometimes you can get around it with something like {% block
