logging: warn() methods and function to be deprecated.

[Jean-Michel Pichavant]

Vinay Sajip wrote:
>> I think that is a real shame - it seems to be gratuitous breakage for almost 
>>     
>
>   
>> zero benefit.  That issue shows that Trac makes heavy use of .warn, I've use 
>> .warn almost exclusively for many years, and code.google.com shows it is used 
>> extensively in the wild.
>>     
>
> Okay, but it's easy enough to change, and people are getting a reasonable amount of time to deal with it.
>
>   
>> Is there still a chance to reconsider?
>>     
>
> I'm not dogmatic about things like this; warn() is just a hangover from a long time ago and bit of a nit, that's all. I suppose I should have removed it when 3.0 was released, but it went under my radar at that time.
>
> Hence my post here, to get feedback from logging users about this proposed change.
>
> Regards,
>
> Vinay Sajip
>   
I'm not using python 3, I'm not sure my feedback matters, but I wouldn't 
mind refactoring warn into warning If I'd have to. It's better to use 
documented API anyway.

JM

PS : I also had an issue with my logging wrappers where I did not 
implement warn, quite confusing the first time I had this error.