Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #19164

Re: python logging filter limitation, looks intentional?

Path csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!newsfeed.kamp.net!newsfeed.kamp.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path <python-python-list@m.gmane.org>
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; 'else:': 0.03; 'differently.': 0.07; 'received:verizon.net': 0.07; 'terry': 0.07; 'tests,': 0.07; 'versions.': 0.07; 'python': 0.08; '>>>>': 0.09; 'failing': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:80.91.229.12': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'received:lo.gmane.org': 0.09; 'subject:python': 0.10; ';-)': 0.12; 'am,': 0.12; '2.7': 0.13; '2:17': 0.16; '3.2,': 0.16; 'additions': 0.16; 'bugs,': 0.16; 'non-trivial': 0.16; 'reedy': 0.16; 'release?': 0.16; 'sajip': 0.16; 'subject:limitation': 0.16; 'subject:logging': 0.16; 'vinay': 0.16; 'workaround': 0.16; 'wrote:': 0.16; 'jan': 0.19; 'checked': 0.20; 'header:In-Reply-To:1': 0.22; 'works.': 0.23; 'code': 0.25; 'pm,': 0.26; 'fix': 0.27; 'pass': 0.28; 'differently': 0.30; 'feature,': 0.30; 'planned': 0.30; 'subject:?': 0.30; 'version': 0.31; 'proposed': 0.32; 'actually': 0.32; 'changes': 0.32; 'idea': 0.32; "isn't": 0.32; 'header:User- Agent:1': 0.33; 'to:addr:python-list': 0.33; 'header:X-Complaints- To:1': 0.34; 'thank': 0.35; 'comment': 0.35; 'but': 0.37; 'received:org': 0.37; 'another': 0.37; 'could': 0.37; 'some': 0.38; 'third': 0.38; 'think': 0.38; 'being': 0.39; 'else': 0.39; 'subject:: ': 0.39; 'change': 0.40; 'to:addr:python.org': 0.40; 'more': 0.61; '19,': 0.68; 'policy,': 0.77; '3.3': 0.91
X-Injected-Via-Gmane http://gmane.org/
To python-list@python.org
From Terry Reedy <tjreedy@udel.edu>
Subject Re: python logging filter limitation, looks intentional?
Date Fri, 20 Jan 2012 15:09:31 -0500
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> <mailman.4849.1326934249.27778.python-list@python.org> <3e4f47f7-ab4c-4a7e-a8ab-a280202c235a@v14g2000vbc.googlegroups.com>
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
X-Gmane-NNTP-Posting-Host pool-74-109-121-73.phlapa.fios.verizon.net
User-Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
In-Reply-To <3e4f47f7-ab4c-4a7e-a8ab-a280202c235a@v14g2000vbc.googlegroups.com>
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.4893.1327090195.27778.python-list@python.org> (permalink)
Lines 31
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1327090195 news.xs4all.nl 6874 [2001:888:2000:d::a6]:35664
X-Complaints-To abuse@xs4all.nl
Xref x330-a1.tempe.blueboxinc.net comp.lang.python:19164

Show key headers only | View raw


On 1/20/2012 2:17 PM, Vinay Sajip wrote:
> On Jan 19, 12:50 am, Terry Reedy<tjre...@udel.edu>  wrote:
>>
>>>> I don't want people to have to code differently for Python 3.3 and for
>>>> older versions.
>>
>> This is not a general policy, else we would never add new features ;-)
>> Do you plan to keep logging feature-frozen forever, or just for another
>> release? (I actually think is a good idea to fix bugs, tests, and docs
>> first.)
>
> Logging isn't by any means feature-frozen - new features are being
> added all the time, including non-trivial additions made in 2.7 and
> 3.2, and some more changes planned for 3.3 and already checked in. My
> comment was about the specific change proposed, which if implemented
> could lead to existing working third party code failing after a Python
> 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. I was thinking of 'code differently' as in

if sys.version.split()[0] >= '3.3': <use snazzy new feature>
else: <use klutzy old workaround>

but that is not a 'have to' as long as the workaround still works.

-- 
Terry Jan Reedy

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


Thread

Re: python logging filter limitation, looks intentional? Terry Reedy <tjreedy@udel.edu> - 2012-01-18 19:50 -0500
  Re: python logging filter limitation, looks intentional? Vinay Sajip <vinay_sajip@yahoo.co.uk> - 2012-01-20 11:17 -0800
    Re: python logging filter limitation, looks intentional? Terry Reedy <tjreedy@udel.edu> - 2012-01-20 15:09 -0500
    Re: python logging filter limitation, looks intentional? Chris Withers <chris@simplistix.co.uk> - 2012-01-28 10:51 +0000
      Re: python logging filter limitation, looks intentional? Vinay Sajip <vinay_sajip@yahoo.co.uk> - 2012-01-29 02:07 -0800

csiph-web