> 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
I'll have to check that out. It looks like it would work fine for my purposes
since I normally run from virtual envs, but could be restrictive in that the
user site-packages isn't added.
I also found some other mentions of this:
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
I'm still not clear on what the problem is with a function that prints code to
be copy pasted. It should probably output to stderr rather than stdout, and
maybe that can be configurable, but I don't think that's what your problem is.
I think that even if you've filtered warnings before, it's
> 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
Kyle Stanley wrote:
> Hmm, I think we may benefit from focusing the efforts on this point (at
> least at first), particularly with regards to making the official
> documentation for the warnings module [1] easier to understand with some
> more examples, or perhaps writing a warnings HOWTO guide
