Re: Should AdminSite be able to handle different namespace?

[crg.m...@gmail.com]

Sent from my HTC

----- Reply message -----
From: "Vajrasky Kok" <sky...@speaklikeaking.com>
To: <django-d...@googlegroups.com>
Subject: Should AdminSite be able to handle different namespace?
Date: Sat, Nov 9, 2013 3:47 pm

Greetings, friends!

This is related with this ticket: https://code.djangoproject.com/ticket/21132

While working on this ticket, I was pondering whether we should really fix this or not because one of the core developers said,

"The whole admin is currently built on the idea that the app is named admin, I think we should just deprecate the app_name argument."

Assuming his/her opinion is valid, my question is "What is the point of fixing something that we would deprecate in a short time?"

Would it be better if we just raise error if someone provided keyword `app_name` argument in AdminSite constructor? This would not break backward-incompatibility because this bug had prevented someone to provide keyword `app_name` anyway.

Thoughts? Of course, it is a different story, if we need to embrace `app_name` keyword argument gleefully.

Cheers,
Vajrasky

--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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/536bd4d2-6eb9-4801-92f6-d874e7f5282c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.