Hi Aymeric, I'm sorry that you feel this has devolved to a bikeshedding fest, that certainly wasn't my intent, and I'd hate to see this issue die. I think we both agree that supporting people's names is important - which is the main thing.
To summarise the available options discussed so far: Status Quo: Do nothing, and fail to handle a large chunk of the world's population who's names don't fit in 30 characters Radical changes (in order of increasing radicalness): - Change fields to a TextField - Replace last_name / first_name with a single "name" field - Change startproject to default to a custom user model with default fields that are in line with W3C recommendations Minimal change: Increase the length of the existing fields As far as I can see, everyone is in favour of the minimal change option NOW, and possibly some of the Radical changes later. So the only remaining disagreement is over the value of max_length to change to. Proposals of 60, 100 and 255 have been made. If I created a patch that set the max_length to 255, would anyone object? If so, what's the objection - storage space shouldn't be a concern, and breaking a form seems as likely with 60 as 255? Cheers, Malcolm On 2 August 2016 at 12:26, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hello Malcolm, > > > On 02 Aug 2016, at 10:28, Malcolm Box <malc...@tellybug.com> wrote: > > > > Having read the W3C Q&A carefully, the relevant comment on field lengths > is "avoid limiting the field size for names in your database". > > Indeed. I chose to propose something else because I didn’t want the > solution to depend on an implementation of “CharField of unlimited length”. > > That feature isn’t hard to implement but it involves more difficult design > decisions. Look at the archives for this mailing-list for more information. > > Anyway, it seems that this issue is bound to die in a bikeshedding fest, > so I’ll leave it there, with my apologies to Brazilian users who will > remain unable to log into Django-based websites :-( > > -- > Aymeric. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/h98-oEi7z7g/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/36DD2C84-E5ED-4646-9857-B6BC5D92BE94%40polytechnique.org > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAF3R4sU%3D1gaTk3AGRY7nuQHFX8op9-b00Frc6z_1k69k_R-bNA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
