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 <remi.lape...@henki.fr> wrote: > Every time I use subprocess.run and others I find myself writing > boilerplate code to log program calls and their results. > > Could we log those directly in subprocess.py so that we could just set a > "subprocess" logger instead? > > Rémi > _______________________________________________ > Python-ideas mailing list -- python-ideas@python.org > To unsubscribe send an email to python-ideas-le...@python.org > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/python-ideas@python.org/message/S5MWG7KM5O42TVVK3GUUXFZTB6LYUROQ/ > Code of Conduct: http://python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/2B7VW5RG2BFRF6425DM7OFGZS3P73RDV/ Code of Conduct: http://python.org/psf/codeofconduct/
