[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v2 0/1] Update check-python-tox test for pylint 2.10
From: |
John Snow |
Subject: |
[PATCH v2 0/1] Update check-python-tox test for pylint 2.10 |
Date: |
Wed, 15 Sep 2021 01:30:10 -0400 |
V2: It's not safe to use sys.stderr.encoding to determine a "console
encoding", because that uses the "current" stderr and not a
hypothetically generic one -- and doing this causes the acceptance tests
to fail.
Use UTF-8 instead.
Question: What encoding do terminal programs use? Is there an inherent
encoding to fprintf et al, or does it just push whatever bytes you put
into it straight into the stdout/stderr pipe?
John Snow (1):
python: Update for pylint 2.10
python/qemu/machine/machine.py | 3 ++-
python/setup.cfg | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
--
2.31.1
- [PATCH v2 0/1] Update check-python-tox test for pylint 2.10,
John Snow <=