Fix encoding warnings with PEP 597 enabled

[danyeaw]

Pull Request Check List

Resolves: #8892

• Added tests for changed code.
• Updated documentation for changed code.

This PR fixes Encoding Warnings with PEP 597 warnings enabled and enables the warnings in CI. There are also a few warnings with poetry-core and cleo, and I can submit PRs for those repos as well.

[radoering]

pre-commit.ci autofix

[radoering]

There are still some warnings we should address.

[danyeaw]

We are down to 1 warning:

tests/console/commands/test_init.py::test_respect_prefer_active_on_init[True-1.1]
  /home/dan/Projects/poetry/tests/console/commands/test_init.py:1091: EncodingWarning: 'encoding' argument not specified.
    result: str = orig_check_output(cmd, *_, **__)

I'm not sure what to do about that one since it is a mocked out version of check_output.

[danyeaw]

Actually 1 more as well:

tests/vcs/git/test_system.py::TestSystemGit::test_clone_success
  /home/dan/Projects/poetry/src/poetry/vcs/git/system.py:43: EncodingWarning: 'encoding' argument not specified.
    subprocess.check_call(

I'm not sure how to apply encodings to a check_call.

[radoering]

I'm not sure what to do about that one since it is a mocked out version of check_output.

The warning comes from calling the original method so I suppose at least one check_output() does not specify an encoding. Did you check that each check_output in the code base specifies an encoding? (Alternatively, you can catch the warning and re-emit it with stacklevel=2 to find the caller.)

I'm not sure how to apply encodings to a check_call.

Probably, the same as for the other methods. According to the docs it supports the same kwargs as Popen.

[danyeaw]

Hi @radoering, I rebased this on top of the main branch. Unfortunately mypy gives a Unexpected keyword argument "encoding" for "check_call".