>>> For the record - I don't think the "multiple versions of a single app" >>> problem is one worth solving. I'm not even convinced it can be solved >>> at all, for all the reasons Florian identified, and then some. >> >> I agree, but IIRC it was quoted as one reason why this feature was >> left out of the running in the recent Django revisions. It doesn't >> make a lot of sense to me for any app where models are concerned, and >> I believe there would be no point in duplicating the models for >> multiple instances of an app. > > Not to my reading. The reason for rejection at official voting has > always been "incomplete design". I can see that the subject of > multi-deployed apps has come up in the past, but it's also been > identified as a *hard* problem, and possibly one that doesn't need > solving. Unless someone can provide a particularly compelling use > case, I'm inclined to put it on the ignore pile.
Having tried to solve this problem myself a while ago, I agree -- multiple app instances are out of scope of the summer of code. Jannis -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
