On 16.08.2012, at 23:38, Russell Keith-Magee <russ...@keith-magee.com> wrote:
> On Fri, Aug 17, 2012 at 5:26 AM, Adrian Holovaty <adr...@holovaty.com> wrote: >> I'd like to move all Django localflavor code into a separate package, >> distributed separately from Django the framework. > > +1. I've had the exact same thought myself over the past couple of > years. My hesitation historically has been the limitations of the > Python packaging environment, but we've pretty much reached the point > with pip et al where that isn't a serious impediment any more. > >> PROPOSED SOLUTION >> >> I think it makes most sense for there to be country-specific packages, >> such as django-forms-us or django-forms-es, that are distributed >> independently. These would be very easy to install (via pip), and >> people outside of the Django core team could maintain them and take >> full responsibility for them. > > I agree that this is certainly one way that we could address the > problem. However, localflavor isn't just forms. Some of the packages > (US in particular; and I think there's also a patch lurking for AU) > have database models as well. I'd be inclined to keep the > 'localflavor' moniker. > > Also, from a project management point of view, there's the issue of > translations. At present, there's a single locale directory that > contains all the translations for all the localflavors. If we break > out localflavor into separate installable directories, we probably > don't want to break them into 40 different locale directories. I won't > profess any particular expertise on translations, so there might be an > obvious and elegant solution that I'm missing, but I wanted to flag it > so that it's kept in mind. This can be handled as we did it with the core translation, splitting it up. It's a bit of work, but totally doable. The basic idea is to copy the main localflavor po file to each sub app and run makemessages on it again. gettext will drop the unneeded message IDs (from the other localflavors) when specifying the --no-obsolete option. 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-developers@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.
