How about requiring that if csrfmiddlewaretoken is set, no matter what http
method (GET, POST...), it is correct otherwise 403 response.
Simon
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receivi
I think this ticket http://code.djangoproject.com/ticket/12386
identifies a change in the m2m code which breaks backwards
compatibility.
Consider the following three apps and models:
AppA/models.py:
class ModelA(models.Model):
name = models.CharField(max_length=1024, default='', blank=True)
Are you using timezone aware datetime objects? If so, see
http://code.djangoproject.com/ticket/10443
Simon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
On Apr 10, 9:44 pm, simonb <[EMAIL PROTECTED]> wrote:
> return unicodedata.normalize('NFC',text)
That should be "return unicodedata.normalize('NFC',value)"
It's late!
Simon
--~--~-~--~~~---~--~~
You receive
On Apr 10, 2:48 pm, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> hi,
>
> would it be a good idea to add support to django to unicode-normalize
> incoming get/post-data?
class NormCharField(forms.CharField):
def clean(self, value):
value = super(NormCharField, self).clean(value)
r
