On 16.08.2012, at 23:48, Łukasz Rekucki <lreku...@gmail.com> wrote:
> On 16 August 2012 23:42, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: >> 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. > > It's not only new, but it works > (http://docs.python.org/dev/whatsnew/3.3.html#pep-420-namespace-packages) > ;) > > On Fri, Aug 17, 2012 at 5:39 AM, Alex Gaynor <alex.gay...@gmail.com> wrote: >> >> >> On Thu, Aug 16, 2012 at 9:38 PM, Russell Keith-Magee >> <russ...@keith-magee.com> wrote: >>> >>> >>> 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. >> >> I don't think that's correct, they have model *fields*, but no actual >> models. > > I'm pretty sure everyone with South will still be pretty unhappy about > updating all their migration files. Updating the South migration files is an unfortunate requirement, but also something that can be done with a simple search/replace when migration to a newer Django version. 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.
