p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Correct a typo in [14541]. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14542 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2010-11-12 16:35:40 +00:00
parent dc0accb5a3
commit bd83177c70
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/releases/1.3-alpha-1.txt
View File

@ -183,7 +183,7 @@ Due to the sensitive nature of passwords, however, Django 1.3 takes
this step automatically; the default value of ``render_value`` is now this step automatically; the default value of ``render_value`` is now
``False``, and developers who want the password value returned to the ``False``, and developers who want the password value returned to the
browser on a submission with errors (the previous behavior) must now browser on a submission with errors (the previous behavior) must now
explicitly indicate this. For ezmple:: explicitly indicate this. For example::
class LoginForm(forms.Form): class LoginForm(forms.Form):
username = forms.CharField(max_length=100) username = forms.CharField(max_length=100)

2
docs/releases/1.3.txt
View File

@ -174,7 +174,7 @@ Due to the sensitive nature of passwords, however, Django 1.3 takes
this step automatically; the default value of ``render_value`` is now this step automatically; the default value of ``render_value`` is now
``False``, and developers who want the password value returned to the ``False``, and developers who want the password value returned to the
browser on a submission with errors (the previous behavior) must now browser on a submission with errors (the previous behavior) must now
explicitly indicate this. For ezmple:: explicitly indicate this. For example::
class LoginForm(forms.Form): class LoginForm(forms.Form):
username = forms.CharField(max_length=100) username = forms.CharField(max_length=100)