Model validation is just about ready to go. I have one small issue
with it, namely with ComplexValidator, which I'll describe below, but
I think we can resolve it fairly easily. Here's a bit of background.
Sorry if you're already familiar with the branch.
Validators are functions that are tied to
> How do you feel about having a default max_length value for a
> models.CharField, so we can use it like:
> class MyModel(models.Model):
> example = models.CharField()
>
> What are the pros and cons?
I'm pretty -1 against it.
Pros:
+ you get to be lazy in one particular use-case, for what
Hi all,
This is just a quick reminder that there will be a development sprint
for Django on January 9-10th in Chicago at the Everyblock offices.
This is just after the major feature freeze so we'll be working on a
bunch of smaller features. If you can make it we'd love if you could
join us. If y
On Friday 01 January 2010 16:45:19 Wim Feijen wrote:
> I am not talking about SafeForm. I am sorry I wasn't clear before,
> but in fact, what I want to propose is to include the lines:
> name='csrfmiddlewaretoken' value='1234567890abcdef etc' />
> by default when rendering a form with {{ form }}
Hi,
How do you feel about having a default max_length value for a
models.CharField, so we can use it like:
class MyModel(models.Model):
example = models.CharField()
?
What are the pros and cons?
Wim
--
You received this message because you are subscribed to the Google Groups
"Django devel
Hi Luke,
Thanks for your quick response.
I've read the discussions about CSRF and SafeForm, in fact I already
did before posting my message. Because of your excellente wiki the
threads were easy to find.
I am not talking about SafeForm. I am sorry I wasn't clear before, but
in fact, what I want
