On Fri, 2007-02-09 at 23:59 -0600, Adrian Holovaty wrote: > On 2/9/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > My recommendation in there is that we stop screwing around with builtins > > and just import the thing directly and alias it in each module. We are > > trying to be too clever. I don't really like breaking Python's existing > > use of _ as we are doing and it's slightly odd behaviour, since almost > > nothing else in Python appears magically like this. > > > > The only reason I have not done this is that whilst it is fine for > > Django core, it more or less immediately breaks all code that uses i18n > > (because they have to do the import in their own code instead of relying > > on Django to have poked into __builtins__). I had mentally put this off > > as a post-0.96, pre-1.0 issue to sort out. > > 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. 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 -~----------~----~----~----~------~----~------~--~---
