Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'suppose': 0.05; 'trac': 0.07; 'python': 0.08; 'matters,': 0.09; 'shame': 0.09; 'wrappers': 0.09; 'api': 0.09; 'benefit.': 0.16; 'okay,': 0.16; 'received:192.168.200': 0.16; 'refactoring': 0.16; 'sajip': 0.16; 'subject:() ': 0.16; 'subject:function': 0.16; 'subject:logging': 0.16; 'vinay': 0.16; 'warn': 0.16; 'cc:addr:python-list': 0.16; 'wrote:': 0.16; "wouldn't": 0.17; 'seems': 0.20; 'cc:2**0': 0.22; 'header:In-Reply-To:1': 0.22; 'documented': 0.23; 'extensively': 0.23; "i'm": 0.27; '3.0': 0.28; 'bit': 0.28; 'anyway.': 0.29; 'cc:addr:python.org': 0.30; 'ago': 0.31; 'shows': 0.32; 'change.': 0.32; 'proposed': 0.32; 'error.': 0.32; 'implement': 0.32; 'it.': 0.33; 'there': 0.33; "i've": 0.34; 'header:User-Agent:1': 0.34; 'quite': 0.34; 'things': 0.34; 'all.': 0.34; 'here,': 0.35; 'post': 0.36; 'issue': 0.36; 'using': 0.37; 'but': 0.37; 'think': 0.38; 'should': 0.38; 'went': 0.38; 'subject:: ': 0.39; 'received:192': 0.39; 'under': 0.39; 'getting': 0.39; 'enough': 0.39; "i'd": 0.40; "it's": 0.40; 'where': 0.40; 'header:Received:6': 0.60; 'heavy': 0.71; 'hangover': 0.84; 'to:addr:yahoo.co.uk': 0.91 X-IronPort-AV: E=Sophos;i="4.69,398,1315173600"; d="scan'208";a="2323276" X-Virus-Scanned: amavisd-new at zimbra.sequans.com Date: Mon, 24 Oct 2011 16:34:32 +0200 From: Jean-Michel Pichavant User-Agent: Mozilla-Thunderbird 2.0.0.24 (X11/20100328) MIME-Version: 1.0 To: Vinay Sajip Subject: Re: logging: warn() methods and function to be deprecated. References: <4EA4A65F.2090205@gmail.com> <1319444908.73851.YahooMailNeo@web25801.mail.ukl.yahoo.com> In-Reply-To: <1319444908.73851.YahooMailNeo@web25801.mail.ukl.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "python-list@python.org" X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 32 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1319466878 news.xs4all.nl 6856 [2001:888:2000:d::a6]:39388 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:14921 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.