On Thu, Aug 16, 2012 at 4:33 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > An added benefit that you didn't mention is easier maintenance -- each > individual localflavor package could have its own maintainer(s), > meaning they wouldn't have to get the attention of a core committer to > get fixes in.
Totally -- that's huge. > One question: would you be thinking of doing some sort of namespace > package deal so that `django.contrib.localflavor.us.Whatever` > continues to work with an externally-installed `django-localflavor-us` > package, or is part of this requiring users to change imports? I have > no real opinion either way -- that is, I'm asking, not telling > </inside-joke>. You mean like a magic import thing, right? I think we should force the issue and require people to change imports -- but they'd have two full Django point versions to do that, per our deprecation policy. The one controversial thing would be requiring people to install their needed django-localflavor-* packages when they upgrade to 1.5. Adrian -- 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.
