Yes, I am.
Yes, at an absolute minimum, having linters report this as an issue would mean that we can find out if it’s a reasonable position to take before we make changes to Python.
But once again I’m confused. I’m not using a UTF-8 console, because as I said a number of times, it breaks my other applications. I thought we’d established that we were only talking about a world where UTF-8 mode would only be enabled when the user has set cp 65001. So what I am saying here, is what problem is being solved by asking users to set cp 65001 on, which would not just as well be solved by asking them to set PYTHONUTF8=1.
Or maybe I’m asking what problems people who have set cp 65001 see that people like me who don’t, are not encountering. And why aren’t we telling those people to either set PYTHONUTF8=1 or to change their code page to something other than 65001? That latter is not a serious suggestion - I don’t expect to ask anyone to change their default codepage just to satisfy Python!
What I’m really asking is for an example of a program that someone could write, which gives the wrong results, so that I can understand the options for fixing that issue and why PEP 597 is a better option than the alternatives.