-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Victor,
On 10/22/2011 06:57 PM, Victor Hooi wrote:
> /Disclaimer: This is about the the Django Docs, and a possible
> suggestion for it - apologies if this isn't the correct group (but I
> didn't think it quite fell into django-users).
No worries, you've got the right list. Developing the Django docs is
part of developing Django, and this list is about developing Django.
> The official Django Docs for forms offers up the following pattern for
> Form view code:
>
> def contact(request):
> if request.method == 'POST': # If the form has been submitted...
> form = ContactForm(request.POST) # A form bound to the POST data
> if form.is_valid(): # All validation rules pass
> # Process the data in form.cleaned_data
> # ...
> return HttpResponseRedirect('/thanks/') # Redirect after
> POST
> else:
> form = ContactForm() # An unbound form
> return render_to_response('contact.html', {
> 'form': form,
> })
>
>
> https://docs.djangoproject.com/en/dev/topics/forms/
>
> I was just viewing a talk by pydanny and Miguel Araujo at DjangoCon US
> 2011 on "Advanced Django Form Usage", and they offered up what they seem
> to feel was a better pattern for form viewcode:
>
> def some_view(request, template_name="someapp/someform.html")
> form = MyForm(request.POST or None)
> if form.is_valid():
> do_x()
> return redirect('Home')
> return render(request, template_name {'form': form}).
>
>
> http://speakerdeck.com/u/pydanny/p/advanced-django-forms-usage (Slide 13)
>
> Now, apart from being shorter, I don't think I know enough about Django
> or forms to know which one is actually "better" overall. However, what's
> the community's consensus on this?
I think this might have been mentioned in an audience question at that
talk: the shorter code does have an edge-case problem. It is possible
for request.method to be "POST" and for request.POST to be empty.
(Browsers generally won't do that, they'll submit empty strings; but
forms are useful for validating data from other sources as well, such as
API clients). For some (less common) forms, this could even be a valid
form submission (if no fields are required). In the other cases, it
should really return a bound, not-valid form, with one or more "This
field is required" validation errors. With the shorter code, it will
instead return the unbound form again.
This problem can be fixed by changing the form instantiation to:
form = MyForm(request.POST if request.method == "POST" else None)
At this point, though, I'm no longer convinced that it's much simpler or
more readable.
The other advantage of the longer version is that if you need to add
request.FILES handling to the form, for instance, it's clearer and
simpler how to do that.
> If it is better, is there any scope for having it in the official Django
> docs? Or even adding it as an alternative approach, and discussing the
> pros/cons?
I think the issues with the short version are subtle and advanced enough
that they'd be a serious distraction at that point in the docs, and the
gain just isn't worth the need to introduce that discussion. The
currently-documented version is good enough (TM), and it's more explicit
about what's going on.
Carl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6jgIIACgkQ8W4rlRKtE2dIzACgt4lh06OKTeCyb1cGPnKKYq8h
twUAoM21MaExW6uLk/DxgUzaKcbwEQFb
=EWnD
-----END PGP SIGNATURE-----
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
