FWIW I agree with Florian:
- Where the default is unsuitable for a project, it's easier to restrict
the field's length in forms than to increase it in the User model.
- It's hard to imagine a situation where a 100-character limit is
suitable but a 150-character limit isn't.
- I ca
On Wednesday, August 10, 2016 at 5:34:44 PM UTC+2, Tom Christie wrote:
>
> I'd always defer towards humanized limits, rather than technical limits,
> so I'd suggest 100 chars seems like a decent cap.
>
Not trying to troll or derail, but can we please make it 150 chars? It is
still kinda "humaniz
Ok.
I agree we can set for an increase to 100 characters :)
Cheers
_
Raony Guimarães Corrêa Do Carmo Lisboa Cardenas
PhD in Bioinformatics
email: raonyguimar...@gmail.com
skype/hangouts: raonyguimaraes
phone: +48 722 148 478
_
> On 10 Aug 2016, at 17:34, Tom Christie wrote:
>
> I'd always defer towards humanized limits, rather than technical limits, so
> I'd suggest 100 chars seems like a decent cap.
Yes.
Repeating my earlier message:
> I’m -1 on basing the decision of “how long a last name does Django allow by
>
I'd always defer towards humanized limits, rather than technical limits, so
I'd suggest 100 chars seems like a decent cap.
--
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
Hi,
Now that this thread went silent for a few days, can we reach a consensus
and try increase last_name to the maximum size available without breaking
backward compatibility ?
Please, lets make Django more available to the rest of the world. This is a
small change with a huge benefit to use
