On Sun, 2007-02-11 at 08:20 +0800, Russell Keith-Magee wrote: > On 2/10/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > > On Fri, 2007-02-09 at 23:59 -0600, Adrian Holovaty wrote: > > > I'm +1 on that change, despite its backwards incompatibility. It > > > doesn't require much brain power to add import statements to code, so > > > it wouldn't be a *huge* inconvenience. > > > > OK, let's do that then. If there's still a chance that 0.96 will come > > out soon-ish, I'd rather wait until after that to make the change, just > > so that people have a clear delineation point for the change. > > Ok. If this is the way we are going to go, I'll make the one line > import change that makes my problem unit test pass, then have a bash > at adding explicit imports everywhere else. I'll leave removing the > builtins definition until post-0.96.
Sounds like a plan. I'll take on the job of removing our insertion of _ into __builtins__ a day or two after 0.96 comes out. Cheers, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
