Documentation needs to declare CalledProcessError as potentially resulting from subprocess.run()

[jennievh]

BPO	43635
Nosy	@jennievh

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2021-03-26.19:47:45.295>
labels = ['type-feature', '3.9', 'docs']
title = 'Documentation needs to declare CalledProcessError as potentially resulting from subprocess.run()'
updated_at = <Date 2021-03-26.19:47:45.295>
user = 'https://github.com/jennievh'

bugs.python.org fields:

activity = <Date 2021-03-26.19:47:45.295>
actor = 'jennievh'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-03-26.19:47:45.295>
creator = 'jennievh'
dependencies = []
files = []
hgrepos = []
issue_num = 43635
keywords = []
message_count = 1.0
messages = ['389564']
nosy_count = 2.0
nosy_names = ['docs@python', 'jennievh']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue43635'
versions = ['Python 3.9']

[jennievh]

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