> Some parts of the stdlib output some logs like urllib, I think only the
> configuration of the handlers is up to the application.
>
> I don't see any logging calls in urllib. If you know of any, can you point me
> to them? (There are some warnings.warn() calls, but that's different.)
I
On Wed, Feb 26, 2020 at 3:58 AM Rémi Lapeyre wrote:
> > Why does this deserve in the stdlib?
> > (The stdlib does very little logging of its own -- logging is up to the
> application.)
>
> Some parts of the stdlib output some logs like urllib, I think only the
> configuration of the handlers is
> But couldn't you just write a simple helper function/class that handles your
> usual workflow?
I do when I’m the one calling subprocess.run() but it’s not possible to do that
when it’s a library that does the call.
> Why does this deserve in the stdlib?
> (The stdlib does very little
On 2/24/20, Guido van Rossum wrote:
>
> The stdlib does very little logging of its own -- logging is up to
> the application.
It's not logging per se, but the standard library does have an
extensive and growing list of audit events that are intended to assist
with testing, logging and security
But couldn't you just write a simple helper function/class that handles
your usual workflow? Why does this deserve in the stdlib? (The stdlib does
very little logging of its own -- logging is up to the application.)
On Mon, Feb 24, 2020 at 2:24 AM Rémi Lapeyre wrote:
> Every time I use
