As I stated at the bottom of my post:

“To make this even more maddening, I have the same setup on a 2012 Mac Mini Server running the same software listed above, and it works.”

Everything is the same across all three machines. But just for the sake of seeing if LTS is better than the current release, first I had brew remove its version, then I downloaded the LTS macOS TAR file, expanded it into a folder all by itself, and set up the PATH to point to this specific one. A simple ‘node –version’ showed it was capable of being executed. When I started up VSCode on the MacBook Pro 15″ and enabled PyMakr, it still showed all the failures.

Removing VSCode completely and then re-installing it again has reached a point where trying to get PyMakr on VSCode and macOS to work properly is pointless. It works with Atom; at this point I don’t care about VSCode anymore. I have too many other projects with VSCode and they all work without issue. The problem is fully with the PyMakr devs; if they choose not to address it, then so be it. I’ve gone as far as reasonably possible, even running VSCode in logging mode with ‘–log trace’, and looking in

~/Library/Application Support/Code/logs/

for any and all resultant log files. What really sent me up a wall is that I found nothing that would help with PyMakr’s issues.

Thanks for the suggestions, but I’m far beyond that point and I’m done.

LikeLike

LikeLike