On Wed, Oct 15, 2008 at 6:38 PM, Jesse Young <[EMAIL PROTECTED]> wrote: > * Existing apps might rely on it being a function. But it's not > documented anywhere, so it doesn't seem like apps should be using it > directly.
I don't know about *should*, but some apps *are*[0]. This would break backwards compatibility on a non-underscored method, so I think making it an attribute is a non-starter, but it might be worth de-currying it. I don't think it can be outright turned into a property or attribute, though. Adam [0]: http://google.com/codesearch?hl=en&lr=&q=related_query_name&sbtn=Search --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
