Message 389564 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	jennievh
Recipients	docs@python, jennievh
Date	2021-03-26.19:47:45
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1616788065.3.0.472312141922.issue43635@roundup.psfhosted.org>
In-reply-to

Content
The documentation for subprocess says that run() can return CalledProcessError... https://docs.python.org/3/library/subprocess.html#subprocess.run ...but when you click on the link (5th paragraph down) for CalledProcessError, it only lists check_call() and check_output() as methods that can return it. My understanding is that check_call(), at least, is (becoming?) deprecated. So this section should definitely mention run(): https://docs.python.org/3/library/subprocess.html#subprocess.CalledProcessError

The documentation for subprocess says that run() can return CalledProcessError...

https://docs.python.org/3/library/subprocess.html#subprocess.run

...but when you click on the link (5th paragraph down) for CalledProcessError, it only lists check_call() and check_output() as methods that can return it.

My understanding is that check_call(), at least, is (becoming?) deprecated. So this section should definitely mention run():

https://docs.python.org/3/library/subprocess.html#subprocess.CalledProcessError

History
Date	User	Action	Args
2021-03-26 19:47:45	jennievh	set	recipients: + jennievh, docs@python
2021-03-26 19:47:45	jennievh	set	messageid: <1616788065.3.0.472312141922.issue43635@roundup.psfhosted.org>
2021-03-26 19:47:45	jennievh	link	issue43635 messages
2021-03-26 19:47:45	jennievh	create