#15089: contrib.sites and multitenancy
---------------------------------------------+------------------------------
Reporter: legutierr | Owner: nobody
Status: new | Milestone:
Component: Contrib apps | Version: 1.3-beta
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------+------------------------------
Changes (by carljm):
* keywords: blocker =>
* needs_better_patch: 0 => 1
* milestone: 1.3 =>
Comment:
I'm not sure why this is marked as 1.3 blocker. Much as I'd like to see it
added, dynamic multitenancy is a new feature for contrib.sites that
belongs in 1.4 at this point. I haven't seen anywhere in this thread a bug
identified in a 1.3 feature. It's not a bug that the new get_current_site
function doesn't support dynamic multitenancy, as contrib.sites has never
supported that, and get_current_site wasn't intended to add support for it
(it was intended to add a RequestSite fallback when contrib.sites is not
installed, and it already does that just fine). So I'm removing the 1.3
milestone and blocker flag - Russell, please feel free to reverse if
there's something obvious I'm missing.
I've posted some more design-decisiony thoughts on the feature and current
patch here: http://groups.google.com/group/django-
developers/msg/c7e3ee09837851c3
--
Ticket URL: <http://code.djangoproject.com/ticket/15089#comment:17>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
