Change level of nesting code

[byBenPuls]

Make code easier to read by reducing the level of nesting. High levels of nesting make code more confusing and less readable.
For example:

if process.returncode == 0:
    return stdout.decode(*DECODE_ARGS)
else:
    raise CalledProcessError(
        process.returncode, args,
        stdout.decode(*DECODE_ARGS), stderr.decode(*DECODE_ARGS)
    )

We can remove else, simplify the code:

if process.returncode == 0:
    return stdout.decode(*DECODE_ARGS)
raise CalledProcessError(
    process.returncode, args,
    stdout.decode(*DECODE_ARGS), stderr.decode(*DECODE_ARGS)
)

[cpython-cla-bot]

All commit authors signed the Contributor License Agreement.

[bedevere-app]

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

[picnixz]

This is a cosmetic change and we don't accept cosmetic changes (with a few exceptions). This is fine as it is and we prefer to avoid such changes to ease backports. I would recommend closing this as not planned (also, this is an internal script)

[mhsmith]

And let me explain as the person who wrote this code, I sometimes find the redundant else more readable, especially when its content is short. With the else, it's immediately obvious that the two blocks are mutually exclusive. Without the else, you have to look at the content of the block to discover that.