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

Groups > comp.lang.python > #19110

Re: python logging filter limitation, looks intentional?

Show all headers | View raw

On 1/18/2012 4:02 PM, Chris Withers wrote:
> On 17/01/2012 10:48, Vinay Sajip wrote:

> How about an option that defaults to "backwards compatibility mode" for
> Python 2.7, flipped the other way in 3.3?

2.7 only gets bug fixes, and this does not seem to be one.

>> It's not a bug, because it's like that by design. I understand that
>> you don't agree with that particular design decision, but it's out
>> there now. What you're asking for isn't unreasonable, but not
>> achievable without a change in behaviour.
>
> See above ;-)
>
>> 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.)

-- 
Terry Jan Reedy

Back to comp.lang.python | Previous | Next — 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