This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients docs@python, ezio.melotti, python-dev, techtonik, vinay.sajip
Date 2011-10-22.11:00:18
SpamBayes Score 5.97689e-13
Marked as misclassified No
Message-id <1319281214.29104.YahooMailNeo@web25802.mail.ukl.yahoo.com>
In-reply-to <1319275113.05.0.175878615547.issue13235@psf.upfronthosting.co.za>
Content
> Just to me it clear - why do you want warn() to be removed aside from code 

> duplication?
> 
> My argument to leave it and document is that it is convenient and makes lines 
> shorter (and won't break existing code). From logging module I also see that 
> there are also logging.WARN aliases that you'll need to deprecate also.

Sorry, I don't agree. I was happy to leave it as is until you raised this issue, but now I think the right thing to do is deprecate and remove warn(). I'm not too fussed about the WARN level, and I can't easily issue a deprecation warning for it as it's a module attribute, so I'll leave it in as an internal implementation detail, for which the usual caveats apply.
History
Date User Action Args
2011-10-22 11:00:19vinay.sajipsetrecipients: + vinay.sajip, techtonik, ezio.melotti, docs@python, python-dev
2011-10-22 11:00:18vinay.sajiplinkissue13235 messages
2011-10-22 11:00:18vinay.sajipcreate