On 8/7/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > This would be great, as long as you could figure out how to make it > backwards compatible. Thanks for volunteering! :-) > > Here are some broad goals/thoughts, IMHO: > > * Users of Django the framework should not be affected in any way. > > * Ideally we should not have to maintain two versions of the codebase.
These two points are certainly in mind; see my reply to Malcolm's reply. In short, Django templates would still be distributed as part of Django, "batteries included" and all, and would also be available as a standalone package. There would be only one codebase, which would get pulled in during packaging. svn externals could be used for the standard "work out of an svn checkout" case. > * Figuring out the settings stuff could be tricky. Absolutely agreed; this is where most of the fun is going to come in. ^_^ > * Consider the case of people who download and use the standalone > template system, then decide to install the whole framework. It would > be nice (but not essential) if they didn't have to have conflicting > versions of the template library installed on their systems. I don't > know anything about the way Twisted modules are distributed (which is > what you alluded to) -- do they have a nice way of solving this > problem? I'd ideally like the Django installer to detect if django.template was already on the system, and drop Django into the same spot. As far as versioning, Django should check for a minimum version of Django templates (i.e., the version at the time of that Django's release), assuming it was already installed on the system; if it detected a version below the minimum, it would be nice for the installer to offer to simply overwrite the entire django namespace. I don't recall offhand how Twisted handles versioning; we can probably get away with a fairly simple system, since there would only be a one-way dependency and only in cases where a user installed standalone Django templates *before* installing full Django (again, Django templates would come with Django in the ordinary case). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
