On Sun, Feb 25, 2007 at 12:51:56AM -0600, Jacob Kaplan-Moss wrote:
> Finally, the URLconf. For the default case (a single admin)::
>
> ('^admin/', include(admin.site.urls()))
>
> And for multiple admins::
>
> ('^admin/', include(admin.site.urls()))
> ('^admin2/', include(second_adm
On Fri, Sep 08, 2006 at 03:18:22AM +0200, Daniel Poelzleithner wrote:
> in myapps/views.py:
> from .models import Somemodel
>
> which will import from myapps/models.py Somemodel
>
> from ..otherapp.models import Othermodel
>
> imports from myapps/../otherapp/models.py -> otherapps/models.py
>
Why does the admin app tie directly to models? Why not applications?
Nate
--~--~-~--~~~---~--~~
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@googlegrou
On Tue, Jan 23, 2007 at 11:47:08PM -0600, Jacob Kaplan-Moss wrote:
> On 1/23/07 9:16 PM, Nate Straz wrote:
> > Why does the admin app tie directly to models? Why not applications?
>
> Because sometimes you want certain models within in app *not* to be
> admin-editable.
Ok
On Thu, Jan 25, 2007 at 06:21:21PM -0600, Adrian Holovaty wrote:
> On 1/24/07, Nate Straz <[EMAIL PROTECTED]> wrote:
> > What if the admin app was really an admin framework inside Django? It
> > could provide a base admin sub-app that applications could extend. That
&g
On Sun, Jan 21, 2007 at 12:24:54PM -0600, Adrian Holovaty wrote:
> On 1/20/07, Honza Kr?l <[EMAIL PROTECTED]> wrote:
> > why not create a function to do that for you..
> > urls.py is after all a python module, so you could just introduce a function
> >
> > urlpatterns = admin_urls_for_model(
> >
