How about a setting to silence TemplateSyntaxErrors? Have the node
renderer just return an empty string instead?
Might sound a bit loose, and obviously this isn't for us Django guys.
It's for regular HTML guys --
- They could make simple template edits to sites without fear of
bringing the
James Bennett wrote:
> if you'd like to try out the new features or go bug-hunting
> in a safe environment, feel free to take it for a sping.
Django-1.1-alpha-1.tar.gz reports:
^^^
$ python -c "import django; print django.VERSION"
(1, 0, 2, 'final', 0)
Deliberate?
Regards,
Chris Lamb wrote:
> Django-1.1-alpha-1.tar.gz reports:
>^^^
>
> $ python -c "import django; print django.VERSION"
> (1, 0, 2, 'final', 0)
>
> Deliberate?
Ignore this; PEBCAK.
Regards,
--
Chris Lamb, UK ch...@chris-lamb.co.uk
Thanks James Bennett for the thoughtful reply, it sounds like the general
consensus is that the choices feature truly is something that the majority
of users wouldn't want (and I'm inclined to defer to the wisdom of Marty and
James B. -- if you guys think it is mostly useless I'll accept that
> This needs to accept kwargs as well. Lets take the use case were
> Markdown it the default. And most of the site is used by trusted users
> so Markdown is not in safe_mode (we allow raw html). But now, we have
> one field (perhaps comments) which is accessable to the general
> untrusted public.
Well he'd have to use an IntegerField, not a ForeignKey, but the same
idea applies - he can do his own validation/etc in the property
handlers.
On Mon, Feb 23, 2009 at 7:27 PM, Jerome Leclanche wrote:
>
> Sounds like that wouldn't work. Django fails on __init__ with invalid
>
James, you nailed it. This is exactly what we need. Well, with one
minor oversight:
On Tue, Feb 24, 2009 at 2:33 AM, James Bennett wrote:
>
[snip]
> How to handle markup override
> =
>
> That is, also, the solution to the problem of how to do a
I'd go for (2) called USState and (4) called USPSState.
Zellyn
--~--~-~--~~~---~--~~
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