django - What are the dangers of not handling 404 in a view? -


the docs teach must provide django either httpresponse or have exception raised. i'm coding relatively small project, choosing ignore proper 404 handling when writing view, instead making sure data exists beforehand don't run 404s.

of course, rather haphazard writing, , provide context how should making these decisions - how not handling 404s in writing views affect things? instance, website explode?

[edit] so, instance, use my_stuff = thing.objects_all() instead of my_stuff = get_object_or_404(thing, pk=thing_id). here, know thing has objects in because created them earlier in admin, , won't removed. so, need worry 404?


Comments

Popular posts from this blog

php - get table cell data from and place a copy in another table -

javascript - Mootools wait with Fx.Morph start -

php - Navigate throught databse rows -