The default auth.form.AuthenticationForm() did not set a max_length for the
password field:
https://github.com/django/django/blob/72f6513ebaa7a3fd43c26300e9a8c430dc07cdb5/django/contrib/auth/forms.py#L120-L126
Ok there is not really a max_length constraint. Because in the end the
auth.models
Hi,
On Tuesday, May 12, 2015 at 4:43:41 AM UTC+2, Steven Berry wrote:
>
> On Monday, May 11, 2015 at 6:30:39 PM UTC-4, Florian Apolloner wrote:
>
>>
>> On Monday, May 11, 2015 at 10:13:03 PM UTC+2, Steven Berry wrote:
>>>
>>> With all that said I'm in favor of what you suggest -- rely on gunicorn
Florian,
I was merely presenting a rhetorical question to illustrate a point.
Perhaps there weren't other available web servers then, but there are now,
as has been pointed out. Prevalence and expectation of TLS/SSL is another
thing that's changed since 2005. We can choose to maintain runserver
I'm facing the same speed issue here. Like Andrew mentioned above, if
initial data is going to be removed and data migrations are the way
forward, even having an option to skip migrations is a problem because we'd
need that data to be populated. Is there something planned for this for
Django 1.