On Mon, Nov 7, 2011 at 3:59 AM, Justin Holmes <[email protected]> wrote: > Chris, > > Your message comes at a time of frequent discourse over the matter of > apps and pluggability. There's no doubt in my mind that a desire > exists in the django community for this functionality, so I'm > certainly +1 on your creation of a patch. There's no single ticket > around which this matter has coalesced - creating a new ticket is > probably a good approach.
Untrue -- #3591 has been the ticket tracking this idea for some time. The ticket even has a patch/branch that is just waiting for review. I've been wanting to do a review for some time, but life has conspired against me... The focus of this branch has been to turn an "Application" into a configurable object; this would allow app designers to define configuration points that are set at time of deployment. The one major aspect that you've described but isn't covered by the current patch on #3591, is the idea of having multiple instance of the same app in a single project. This introduces the complication that database table names need to include a deploy-time component (i.e., some sort of instance identifier), which, IIRC, was punted from the goal list for the SoC project that yielded this patch. However, to the best of my knowledge, the approach described in the current patch *could* be used to handle the multiple instance scenario; it just hasn't been implemented. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
