Closed ncoghlan closed 3 weeks ago
And the whole reason this test case uses run_python_command_unchecked
is so it gets the same "Keep subprocesses from screwing up their text encodings" as venvstacks
itself uses: https://github.com/lmstudio-ai/venvstacks/blob/bb1c7e9b2eb9ba7f0df36a6950cfa92aaefdaf23/src/venvstacks/_util.py#L63
Turned out this was a real problem with the encoding handling when communicating with subprocesses: https://github.com/lmstudio-ai/venvstacks/pull/46
The reason the Windows CI was the one that picked it up is because it defaults to cp1252 instead of utf-8.
In #41
test_entry_point_help
fails in the Windows CI with:This isn't a general Windows command execution problem, since
venvstacks
runs a lot of subcommands of its own, and the project tests run various queries in the target Python environments that will include Unicode characters in their results.It's being worked around with an
xfail
for now, since this is a stock standard entry point definition, so the problem is almost certainly in the test suite or the test environment setup.