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

Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!cs.uu.nl!news.stack.nl!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path	<mcfletch@vrplumber.com>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.011
X-Spam-Evidence	'H': 0.98; 'S': 0.00; 'suppose': 0.05; 'trac': 0.07; 'alias': 0.09; 'shame': 0.09; 'am,': 0.12; 'benefit.': 0.16; 'okay,': 0.16; 'sajip': 0.16; 'subject:() ': 0.16; 'subject:function': 0.16; 'subject:logging': 0.16; 'vinay': 0.16; 'url:blog': 0.16; 'written': 0.16; 'wrote:': 0.16; 'seems': 0.20; 'suggest': 0.20; 'header:In-Reply-To:1': 0.22; 'extensively': 0.23; 'code': 0.25; "i'm": 0.27; 'all,': 0.28; '3.0': 0.28; 'bit': 0.28; 'undocumented': 0.30; 'ago': 0.31; 'programmers': 0.31; 'skip:_ 40': 0.31; 'shows': 0.32; 'change.': 0.32; 'proposed': 0.32; 'it.': 0.33; 'actually': 0.33; 'there': 0.33; 'to:addr :python-list': 0.33; 'instead': 0.33; "i've": 0.34; 'header:User- Agent:1': 0.34; 'things': 0.34; 'all.': 0.34; 'here,': 0.35; 'uses': 0.35; 'post': 0.36; 'issue': 0.36; 'skip:" 10': 0.36; 'but': 0.37; 'think': 0.38; 'mike': 0.38; 'should': 0.38; 'went': 0.38; 'subject:: ': 0.39; 'received:192': 0.39; 'under': 0.39; 'characters': 0.39; 'getting': 0.39; 'finding': 0.39; 'enough': 0.39; 'to:addr:python.org': 0.39; "i'd": 0.40; "it's": 0.40; 'provided': 0.60; 'received:208': 0.60; 'here.': 0.66; 'heavy': 0.71; 'hangover': 0.84; 'myself)': 0.84
Date	Mon, 24 Oct 2011 10:38:55 -0400
From	"Mike C. Fletcher" <mcfletch@vrplumber.com>
User-Agent	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version	1.0
To	python-list@python.org
Subject	Re: logging: warn() methods and function to be deprecated.
References	<loom.20111022T135016-802@post.gmane.org> <4EA4A65F.2090205@gmail.com> <1319444908.73851.YahooMailNeo@web25801.mail.ukl.yahoo.com>
In-Reply-To	<1319444908.73851.YahooMailNeo@web25801.mail.ukl.yahoo.com>
X-Enigmail-Version	1.1.2
Content-Type	text/plain; charset=ISO-8859-1
Content-Transfer-Encoding	7bit
X-BeenThere	python-list@python.org
X-Mailman-Version	2.1.12
Precedence	list
List-Id	General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe	<http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive	<http://mail.python.org/pipermail/python-list>
List-Post	<mailto:python-list@python.org>
List-Help	<mailto:python-list-request@python.org?subject=help>
List-Subscribe	<http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups	comp.lang.python
Message-ID	<mailman.2179.1319467505.27778.python-list@python.org> (permalink)
Lines	35
NNTP-Posting-Host	2001:888:2000:d::a6
X-Trace	1319467505 news.xs4all.nl 6891 [2001:888:2000:d::a6]:53059
X-Complaints-To	abuse@xs4all.nl
Xref	x330-a1.tempe.blueboxinc.net comp.lang.python:14922

Show key headers only | View raw

On 11-10-24 04:28 AM, 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.
I'd have to echo Mark's sentiment here.  There is a *lot* of (fairly
old) code around that uses .warn, and I'd wager even a lot of new code
written by old programmers (such as myself) that uses it.  Breaking it
to avoid having an undocumented method seems wrong; suggest just adding
documentation:

    "logger.warn(...) -- an alias to logger.warning provided for
backward compatibility"

>> 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.
I actually consider .warning() a nit :) .  After all, it's 3 extra
characters :) , and *who* actually reads documentation instead of just
poking around and finding the shortest-named method in the instance?

Anyway, I personally don't see this as worth the breakage.

Just my $0.02,
Mike

-- 
________________________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://www.vrplumber.com
  http://blog.vrplumber.com

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: logging: warn() methods and function to be deprecated. "Mike C. Fletcher" <mcfletch@vrplumber.com> - 2011-10-24 10:38 -0400

csiph-web