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, > > get_list_or_404). If we are going to go for the "from > > module_importing_everything_you_might_need import *" approach then > > django.shortcuts would be a good name - but it wasn't what I originally > > had in mind. > > Yeah, I also saw django.shortcuts as the new name for > django.core.extensions -- the functions that wrap a bunch of Django > functionality into one-liners. I'm not so sure we need a module that > includes *every* commonly-used module and function in Django. > > If the end goal is to cut down on the number of imports in view > modules, we will have already gone a long way by trimming the current > four or five lines to the following: > > from django import http, template, shortcuts
That works for me. I think Jacob's 'tasks' email in that thread stuck in my mind the most... adding django.tasks.templatetags, django.tasks.views, etc. for common tasks. Here's a link to that message if you want to revisit it: http://groups.google.com/group/django-developers/tree/browse_frm/thread/d52bdebe380ea23f/d764a9c759cbe08a?rnum=1&_done=%2Fgroup%2Fdjango-developers%2Fbrowse_frm%2Fthread%2Fd52bdebe380ea23f%2F18e9753e7386a0dd%3Ftvc%3D1%26#doc_450a1c40768fcb60 Joseph
