Re: status of 1.10 release blockers

Le vendredi 17 juin 2016 16:52:50 UTC+2, Tim Graham a écrit : > > There are a few small issues to finish up, but if all goes well, the beta > release will happen sometime tomorrow (at least 24 hours from now). > I'm a bit worried about https://code.djangoproject.com/ticket/26719 which could

Re: status of 1.10 release blockers

There are a few small issues to finish up, but if all goes well, the beta release will happen sometime tomorrow (at least 24 hours from now). On Thursday, May 19, 2016 at 2:08:59 PM UTC-4, Tim Graham wrote: > > The CSRF patch is merged. I'm a bit stuck on the middleware one, however, > I don't

Re: Would a patch to add allow_empty_strings=True to CharField be accepted?

Would recent commit solve the problem for you: https://github.com/django/django/commit/267dc4a2882182f71a7f285a06b1d4b15af0 Relevant ticket: https://code.djangoproject.com/ticket/4136 On Fri, Jun 17, 2016 at 3:27 AM, Luke Benstead wrote: > Hi! > > We've recently hit upon

Would a patch to add allow_empty_strings=True to CharField be accepted?

Hi! We've recently hit upon a problem where we need empty strings in a CharField to be coerced to NULL. Obviously nullable CharField's are frowned upon but we have the requirement that non-empty values must be unique, so the empty state must be NULL. We've written a custom subclass of