On 04/10/11 05:56, Tai Lee wrote: > > > On Oct 4, 11:17 am, Russell Keith-Magee <russ...@keith-magee.com> > wrote: >> I'm completely agreed that the 'soft' deprecation is useful. I'm just >> complaining about the ambiguity in the language: "We're deprecating >> this feature by marking it PendingDeprecation...". > > What about just changing "PendingDeprecation..." to > "SoftDeprecation..." or "QuietDeprecation..."? It's not really pending > deprecation. It is deprecated already, but we just don't loudly > complain (yet) if people haven't updated their code immediately.
PendingDeprecationWarning and DeprecationWarning are Python builtins: http://docs.python.org/library/exceptions.html so we can't change the names unless we want to introduce our own alternative, which would definitely be a bad idea IMO. PendingDeprecation is already quiet by default. Regards, Luke -- "I was sad because I had no shoes, until I met a man who had no feet. So I said, "Got any shoes you're not using?" (Steven Wright) Luke Plant || http://lukeplant.me.uk/ -- 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.
