Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.datemas.de!feeder.erje.net!xlned.com!feeder3.xlned.com!amsnews11.chello.com!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.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'behave': 0.07; 'differently.': 0.07; 'terry': 0.07; 'python': 0.08; 'from:addr:simplistix.co.uk': 0.09; 'from:name:chris withers': 0.09; 'message-id:@simplistix.co.uk': 0.09; 'received:89.151': 0.09; 'received:89.151.125': 0.09; 'received:89.151.125.140': 0.09; 'received:server1.simplistix.co.uk': 0.09; 'received:simplistix.co.uk': 0.09; 'subject:python': 0.10; ';-)': 0.12; 'cc:addr:python-list': 0.15; 'behaviour,': 0.16; 'received:93.89': 0.16; 'received:93.89.128': 0.16; 'received:93.89.128.162': 0.16; 'received:buzzkill.local': 0.16; 'reedy': 0.16; 'simplistix': 0.16; 'subject:limitation': 0.16; 'subject:logging': 0.16; 'url:simplistix': 0.16; 'wrote:': 0.16; 'cheers,': 0.20; 'cc:no real name:2**0': 0.21; 'header:In-Reply- To:1': 0.22; 'from:addr:chris': 0.23; 'cc:2**0': 0.25; "wasn't": 0.25; 'expect': 0.26; 'asking': 0.27; 'pass': 0.28; 'cc:addr:python.org': 0.29; 'clear,': 0.30; 'feature,': 0.30; 'chris': 0.30; 'subject:?': 0.30; 'framework': 0.30; 'version': 0.31; 'proposed': 0.32; "isn't": 0.32; 'header:User-Agent:1': 0.33; 'thank': 0.35; 'option': 0.39; 'processing': 0.39; 'subject:: ': 0.39; 'change': 0.40; 'url:uk': 0.40; 'most': 0.60; 'url:co': 0.63; 'received:89': 0.65; 'received:93': 0.78 Date: Sat, 28 Jan 2012 10:51:23 +0000 From: Chris Withers User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Terry Reedy Subject: Re: python logging filter limitation, looks intentional? References: <4F1421C3.6060806@simplistix.co.uk> <1326726505.66259.YahooMailNeo@web25803.mail.ukl.yahoo.com> <4F146EFD.8090102@simplistix.co.uk> <1326756115.24713.YahooMailNeo@web25806.mail.ukl.yahoo.com> <4F151017.6020201@simplistix.co.uk> <1326797302.16852.YahooMailNeo@web25806.mail.ukl.yahoo.com> <4F173369.9010501@simplistix.co.uk> <3e4f47f7-ab4c-4a7e-a8ab-a280202c235a@v14g2000vbc.googlegroups.com> In-Reply-To: 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: 19 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1327754203 news.xs4all.nl 6904 [2001:888:2000:d::a6]:51061 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:19546 On 20/01/2012 20:09, Terry Reedy wrote: >> version upgrade. The proposed change isn't a new feature, it's a >> request for an existing feature to work differently. > > Thank you for the clarification. I had not gotten that the request was > for a change, which has a much higher bar to pass than feature > additions. To be clear, I wasn't asking for a change to existing behaviour, I was asking for the addition of an option that would allow the logging framework to behave as most people would expect when it comes to filters ;-) cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk