Reading today the post
Get user input in Atom while running Ruby script, there was an answer from @ioquatix that had me curious about the promoted package.
From the README.md of the Script Runner Package some interesting detail.
If you get issues about loading
node-pty, you might have a problem with your python install.
node-gyp doesn’t work if
python points to python3. To fix this, tell apm to prefer python2.7
apm config set python $(which python2.7)
Once you’ve done this, reinstall script-runner.
I know I have removed Python V2.7 from my system. Up to recently I only had Python V3.6 (ignoring V2.7 installed with Notepad++). I have also seen that the
windows-build-tools downloaded Python V2.7 before I interrupted the process. So I thought it was worth try on the BETA version of Atom.
Click for spoiler: It did not work.
I installed Python V2.7.
(a) The following were the steps in the command line:
C:\Windows\system32>cd C:\Atom Beta\Atom V1.20
C:\Atom Beta\Atom V1.20>cd resources\app\apm\bin
C:\Atom Beta\Atom V1.20\resources\app\apm\bin>apm config set python C:\Python27
- (b) Confirmation:
C:\Atom Beta\Atom V1.20\resources\app\apm\bin>apm config get python
Restart Atom & reinstall the
Result: No change.
Special note: The package did not request to (?)compile (red bug) as it did the first time I installed it. Not sure how to force this action. Updating dependencies does not change anything either.
What I do know is that Python V3.6 is loaded in my
PATH. I am unsure if it will help to point to V2.7 instead. Or perhaps something else to do with the environmental settings. Perhaps…
Before I retry the monster compiler package - will the minimized C compiler (mingw-w64-install.exe) help for my case? How to test?
Some ideas would be welcome.