On Thu, Aug 16, 2012 at 3:38 PM, Adrian Holovaty <adr...@holovaty.com> wrote: > You mean like a magic import thing, right?
Well, Python *does* have some namespace package support stuff. It's something of a mess, with one implementation internally, another in setuptools, and (IIRC) a new PEP that'll take hold in Python 3 and clean things up. But yeah, it's a mess, and I'm not sure that backwards-compatibility here is really *that* big a deal. Changing imports certainly is pretty easy. > 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. I think that's more sane, though I do think 1.5 is too early to pull the rug out. Perhaps we can do something when we package 1.5 that includes the broken-out packages, with warnings that django-localflavor-xx isn't installed and that in 1.6 they'll need to. Now I'm just thinking out loud though, not sure exactly what the right balance between doing things right and not pissing off users is. Jacob -- 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.
