matheger

Interesting. With the 3.10.2 kernel from conda-forge, it works for me as well. It might be just that one binary that makes it run into trouble. (Having spyder-kernels installed also...

I've found the problem. The `spyder.utils.programs.check_python_help` method checks for a valid python interpreter by essentially running `subprocess.Popen([, '-c', 'import this'], env=, ...)` and making sure that it yields the correct...

Okay, this is weird, but I shuffled a couple 3.10 subversions around because I wanted to know which ones would work and now I can't reproduce the `Popen` error from...

> The idea is to verify that the Python executable can actually run code. If you have other ideas for such a check, we're welcome to hear them. Well, if...

> If so, I do not really understand why the length of the path would be a trouble here, since win10 64 should be able to manage it. I have...

Fixed the problem. On line 30: ` set set SELF=%~f0` Enclose the `%~f0` in double quotes. On line 98: ` set LOG=%LOGD%` Replace the percent signs with exclamation points: `!LOGD!`

I figured that it was only related to logging, and due to some sort of string escaping, which seemed really unfortunate that it broke the whole thing. With those fixes...