On Sun, Nov 10, 2013 at 7:47 PM, Florian Apolloner <[email protected]>wrote:
> Hi Russ, > > > On Saturday, November 9, 2013 11:34:53 PM UTC+1, Russell Keith-Magee wrote: >> >> I'm a little concerned about this talk about deprecation here -- the >> app_name exists for a reason, and at time the app_name feature was added, >> it worked (to the best of my knowledge, anyway). >> > > It most likely did, till we switched the admin to not use hardcoded URLs: > https://github.com/django/django/commit/aaf77c1676e44019abe544911ff7a06eb2690295-- > I have to say that I completely missed app_name there since the tests > didn't seem to cover it and URL namespaces had been kind of a blackbox to > me. That said; we changed this two years ago, so my question is: is this a > feature we want to have? Also I'd appreciate if you can come up with a few > ideas of how to fix it and probably explain the rationale for adding it in > the first place so I can understand how this was ment to be used. > The use case was simple -- deploy two instances of admin in a single project. For example, you might have a truly 'access-all-areas' admin, and a cut down/modified admin for trusted editors that has specially customised workflows, etc. Admin has been specifically designed to allow this, and it's a documented feature [1]. [1] https://docs.djangoproject.com/en/1.0/ref/contrib/admin/#multiple-admin-sites-in-the-same-urlconf Is this a feature we want? Well, I've never used it myself; and the fact that nobody has complained until now suggests that it's not especially well used. On the broader conceptual point, I see value in being able to isolate deployments of a block of URLs… but again, I can't say this is something I'm using. As for how to fix it -- that's a bigger question. It's been a while since I spelunked in that particular code, so I'd need to go digging to offer an opinion. Russ %- ) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84-c0QAy2nrrJT9okUSjAzPDwzhS2yEc3SVasU2jc2870w%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
