a closer look into the Windows Terminal Properties seems to indicate that pyenv changes the code page:
The default code page on my system is 437 (OEM - United States) _prior_ to invoking pyenvand1250 (ANSI - Central Europe` afterwards.

Yes, we are changing code pages in the following lines

• pyenv.bat L3
• pyenv-lib.vbs L264
• pyenv-lib.vbs L272

Yes, we are changing code pages in the following lines [..]

Why does pyenv change the code pages?

I see some issues with it in one of my docker images...

Hej @sunavlis

I think I am facing the same issue on a win-servercore image, any updates on this?

I see there are suggestions in place here in #270

I got bit by this problem too, where a file-read from a different program would work before Python is called, but would fail afterwards due to a change in codepages. My workaround right now is to add a chcp 65001 to reset it to what it was before the python call, but it's very annoying.

As far as I'm seeing from #88, chcp 65001 works fine for Python3 doesn't it? It's the default codepage for Windows if you enable UTF-8 support too, and it's the natural best codepage.

One idea is to make it conditional so that:

• if running any version of Python3, use chcp 65001
• if running any Python2, use chcp 1250
• and the codepage gets reset to whatever it was after execution to prevent lingering effects as it does now

However, this'll still suffer from problems if you do any subprocess calls from Python, since they'll see a different codepage to what you see.

Another thought entirely (and one I like much more) is that pyenv-win shouldn't try to manage codepages at all. The root cause of all of this is #51, which mostly would've been fixed had the user changed their codepage in advance. I feel like it's an expected problem they encountered, and one they would've encountered anyway with other programs too (probably even a regular Python2 install too). It's one pyenv-win isn't obliged to try to fix. People have different codepages. A tool shouldn't try to change essentially a terminal/system setting silently, causing inconveniences for the rest of us who are happy with their use of codepages.

So my suggestion is to remove that chcp command entirely from the batch scripts. Thoughts?