> Nowadays I just go for a single and long name field and I would like to suggest that django.contrib.auth takes this path too because the first name and last name system isn't international and django is for building websites on internet which is meant to be a communication tool connecting Humans of the world, no matter if they have a first and last name or not.
I think having a single name field is reasonable for the vast majority of cases, but it fails where projects really do need to identify two names for things like sorting or categorising. I'd be willing to argue that if you did need to differentiate between parts of a full name then you could customise your User model to account for that. The issue is backward compatibility. We can't just use migrations to remove the last name field because that would break working code and potentially delete data. It'd break a lot more than simply increasing the size of existing labels. I'm +0 on increasing the length of first name and last name. Separately but related - I'd be interested in a discussion around what Django could do to encourage new projects to always customise their user model. Something like having the startproject command include a models file containing a user model ready to be customised, and the setting AUTH_USER_MODEL correctly pointing to it (perhaps with switches to switch between different user models?). So many people run into issues by not customising their user model right at the beginning of their project, and we get into positions where users are unable to properly fix problems they have with the user model and ask for modifications to the default user model like we're seeing here. Regards, Josh -- 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/15f6dbeb-65c3-4a28-b084-80fffb8d81b5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
