Report for week ending September 5, 2015:
Triaged
---
https://code.djangoproject.com/ticket/25330 - RuntimeError: Error creating
new content types." when upgrading to 1.8: due to contenttype.name
(duplicate)
https://code.djangoproject.com/ticket/25338 - IOError exception information
ge
Well, I would prefer asking for confirmation ;-) but not enough to write the
code myself.
--
Aymeric.
> On 5 sept. 2015, at 10:54, Markus Holtermann wrote:
>
> Hey Aymeric,
>
> I think I'd prefer "downgrade the message to a warning and proceed" for
> DEBUG=True and list all validation err
Hey Aymeric,
I think I'd prefer "downgrade the message to a warning and proceed" for
DEBUG=True and list all validation errors, much like for forms. Sticking to
the current implementation for DEBUG=False is fine with me. For example:
$ python manage.py createsuperuser
Username (leave blank to u
Hello,
Indeed, this will be annoying for development.
I don’t find the “admins don’t need rules, they know what they’re doing”
argument compelling. The cobbler children’s go barefoot… Besides, if admins
know the rules, having validation enabled won’t hurt :-)
I’m in favor of implementing an es
