On 1/17/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 1/17/06, kmh <[EMAIL PROTECTED]> wrote:
> > My original idea for django.shortcuts was to hold the functions that
> > wrap up a bunch of Django functionality into a one-liner
> > (render_to_response, render_to_string, get_object_or_404,
On 1/17/06, kmh <[EMAIL PROTECTED]> wrote:
> My original idea for django.shortcuts was to hold the functions that
> wrap up a bunch of Django functionality into a one-liner
> (render_to_response, render_to_string, get_object_or_404,
> get_list_or_404). If we are going to go for the "from
> module
Joseph Kocherhans wrote:
> Here's what I've come up with for django.shorcuts.views. Anything I've
> missed? Anything that should *not* be included? I think this covers
> basic to advanced views and should really simply the first 10 lines of
> most people's view modules. I've left out any kind or a
from django.core.exceptions import ObjectDoesNotExist, PermissionDenied
?
I raise this if somebody GETs to a POST-only view or vice-versa.
On a related note (but probably on the wrong list), what exceptions
do people raise to push errors back to the browser? I have a RESTful
application w
Here's what I've come up with for django.shorcuts.views. Anything I've
missed? Anything that should *not* be included? I think this covers
basic to advanced views and should really simply the first 10 lines of
most people's view modules. I've left out any kind or auth
decorators/exceptions/etc. I'
