For a long time I was having problems to login to djangopackages.com using my github account (pydanny/djangopackages#338).
After investigating I discovered the problem was because my surname is longer than 30 characters. I don't know why both first_name and last_name fields have the same size limit of 30 characters in Django. That doesn't sound very reasonable.
I'm sure there are other people on the same
situation and this already happened with me trying to login in other django websites.
Tim Graham suggested I should first ask on this maillist (https://github.com/django/django/pull/6988#issuecomment-235945422) to see if there is consensus to make the change.
I would like to ask your opinion about an increase from 30 to 60 characters on last_name field so that my login and others won't break again in the future. I can create a Trac ticket if the response is positive.
Kind Regards,
Indeed first and last name dont make sense en various culture. In the Memopol project for exampe where wé have a table of European Parliament representative we have all sorts of names including (The Earl Of) name suffix which is part of the reasons our first / last name system was completely checkmated.
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.
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 change to "Full name" field ?
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/CALC3KaeTBeRU-S2Kk_639ikFP7Z7rxc7LAV17qcDfHM63ATh%3Dw%40mail.gmail.com.
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/ED879BC4-F89D-48D6-9B09-2778FBDBF998%40polytechnique.org.
> On 30 Jul 2016, at 23:15, Donald Stufft <don...@stufft.io> wrote:
>
> See #6 of https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
I’m aware of this article. It's a entertaining read but, unlike the W3 Q&A mentioned earlier, it doesn’t contain actionable advice for designing a generic system that won’t perform too poorly in many use cases when you have no idea of what these use cases will be.
Last names containing over 30 characters are sufficiently common — likely tens of millions of people at this time — to deserve consideration. That’s where this thread started. Let’s not block an easy win for these tens of millions because the general problem is intractable. Besides, a last_name field is already a severe simplification, as we all know.
Last names containing over 100 characters are sufficiently uncommon to be the subject of trivia articles on the Internet. I’m absolutely certain that no website has tens or thousands of millions of last names over 100 characters; in fact, not even tens of such names.
If someone has access to real-life stats from a very large database of names in a country that has long last names that could help us make an optimal decision.
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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.
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/CALC3KaeNyMhAeG0_4L_j0KDg5hV_eAzucy42G1xiLMmfyHOtVQ%40mail.gmail.com.
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/CAABi-DoVpZoTCKL9Mw-J%3DrSJhHFR1jo-WCr9gTVAa%2BBKWbsCjQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAF3R4sVikNLgr1DVtKw_3ps7gFuHrZbO3K1Zhv14ZuUzM5zR0A%40mail.gmail.com.
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/20160802151714.GG5430%40koniiiik.org.
Hi,
> 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 :-(
Please don't let this issue die because we cannot reach consensus between 60, 100, 192 and 255. That would be silly. Django deserves better.
My personal gut feeling is that I prefer something higher than 60 (because why not), but Aymeric has made valid arguments for 60: the practically very relevant example of Portugese / Brazilian names plus some margin. If 60 is a value that allows us to move this forward without making a core developer feel bad about the change, let's go with 60.
I'm +1 on any limit 60+ and -1 on keeping the current limit.
--
René Fleschenberg
--
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+unsubscribe@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/8076F842-B9A7-4772-83B7-80ADC93AAB7C%40polytechnique.org.
I'd always defer towards humanized limits, rather than technical limits, so I'd suggest 100 chars seems like a decent cap.