[Python-ideas] Logging2 with default NullHandler

anatoly techtonik techtonik at gmail.com
Fri Mar 16 17:03:56 CET 2012

On Fri, Mar 16, 2012 at 2:39 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Thu, Mar 15, 2012 at 5:28 AM, anatoly techtonik <techtonik at gmail.com> wrote:
>> logging can not be changed, and leaving everything as-is is a PITA,
>> that's why I am
>> proposing for logging2 as the only viable solution.
> Logging *can* be changed, and indeed *was* changed for 3.2 (to behave
> as Paul describes elsewhere in the thread).

Even though Paul described 2.7 version too, it is good to know that at
least this inconsistency was fixed in 3.x. Sorry for not being clear
about Python 2.x from the start. Seeing that Paul resorted to protect
only `py` 3.2 in the last comment I may assume that we are all agree
that using logging from libraries with scenarios I've described in
Python 2.x is a PITA and all my arguments are valid against this

> Anatoly, when you have complaints like this, *please* check that the
> behaviour you dislike can be reproduced on the latest version of
> Python.

It is hard to propose something for the thing I don't use daily. I
couldn't reproduce this stuff, because getting to the root of the
problem required a lot of effort alone. If there was a list for known
misbehaviours like this in Python 2.x the things could be much easier.

I guess the question can be closed, but I am still dissatisfied with
the current state of things. If Python 3.x is developed using the same
process, there is a risk of UX problems like this too.
anatoly t.

More information about the Python-ideas mailing list