Fellow Report - July 30, 2016

Triaged --- https://code.djangoproject.com/ticket/26941 - Remove quotes from uwsgi "env = LANG=…" configuration (fixed) https://code.djangoproject.com/ticket/26935 - DB connections stuck in closed state when using Django ORM in daemon (duplicate)

Re: status of 1.10 release blockers

The final release is on schedule for Monday, August 1. On Thursday, July 14, 2016 at 10:05:39 AM UTC-4, Markus Holtermann wrote: > > Thank you for the update, Tim. > > #26888 will be taken care of by tomorrow. Either Marten or I are pushing > a PR. > > Cheers, > > /Markus > > On Thu, Jul 14,

Re: Extend support for long surnames in Django Auth

> On Jul 30, 2016, at 4:40 PM, Aymeric Augustin > wrote: > > I have trouble believing that a significant number of people are used to > typing 100+ characters when inputting their name into a website — let alone > that a significant number of people have a

Re: Extend support for long surnames in Django Auth

Hello, > On 30 Jul 2016, at 10:52, Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas > wrote: > > So I'm suggesting a change from 30 to 255 characters on last_name field, > which is the maximum possible without breaking backwards compatibility. I’m -1 on basing the

Re: Extend support for long surnames in Django Auth

On Saturday, July 30, 2016 at 3:25:35 PM UTC+2, Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas wrote: > > So I'm suggesting a change from 30 to 255 characters on last_name field, > which is the maximum possible without breaking backwards compatibility. > Maybe on Django 3 we can propose a

Re: Extend support for long surnames in Django Auth

Hello all, here are my thoughts after reading the discussion. @Erik You won on having the biggest name! Regarding your question about "how long is long enough", after checking other web frameworks such as rails