On Wed, 2007-08-08 at 00:27 -0500, Tom Tobin wrote: > On 8/7/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: [...] > > * Figuring out the settings stuff could be tricky. > > Absolutely agreed; this is where most of the fun is going to come in. ^_^
A couple of other areas are going to be at least equally as interesting... (1) Splitting out the pieces from django.utils that are just used by the template system and moving them under django.templates (preferably in a backwards compatible way, but that's probably easy once you work out the bits). (2) Internationalization is going to be the real creative problem: you'll need to ship a duplicate of django.utils.translation somehow. Also split out the template (and template support code) related messages from the PO files and ship the appropriate message catalogs. This can possibly be done with a bit of gettext hackery. Splitting the translations into two source files in each case files is a bit unfair on the translators, I wouldn't want to do that. There will be a number of duplicate strings and twice as many files for them to maintain. Other areas of duplication are things like the local flavor data and other locale-dependent information. It's pretty likely that locale-aware formatting and validation logically belong together (for maintenance and testing purposes, for a start) and the presentation side is used in more places than just template rendering. The amount of support baggage needed is non-trivial once you factor in i18n support and shared code from places like django.utils, which is why I'm unconvinced this achieves any real benefit. It's like somebody hoping to trim timezone files form their laptop just because they only live in the Australia and don't expect to travel, or worrying that Python installs the array module when they aren't likely to use it. The fact of life is that people install small amounts of code they don't use all the time and don't ever give it a second thought. The extra overhead just to ship everything is truly minor. Regards, Malcolm -- Experience is something you don't get until just after you need it. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---