parpar releases doesnt work with python

[kobayashi90]

parpar releases doesnt work with python, please fix that..

[animetosho]

ParPar is built on NodeJS, not Python.

[ayniin]

When i try to call parpar.exe from python as a subprocess or with os.system. I get an error nodejs error.
inspector.js:25
throw new ERR_INSPECTOR_NOT_AVAILABLE();
^

Error [ERR_INSPECTOR_NOT_AVAILABLE]: Inspector is not available
at inspector.js:25:9
at NativeModule.compileForInternalLoader (internal/bootstrap/loaders.js:277:7)
at NativeModule.compileForPublicLoader (internal/bootstrap/loaders.js:219:10)
at loadNativeModule (internal/modules/cjs/helpers.js:26:9)
at Function.Module._load (internal/modules/cjs/loader.js:679:15)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at bootloader.bundle.cdp:8:210
at Object. (bootloader.bundle.cdp:8:9013)
at Module._compile (internal/modules/cjs/loader.js:999:30) {
code: 'ERR_INSPECTOR_NOT_AVAILABLE'
}

[animetosho]

I tested the following script on Python 3.10:

import os
print(os.system("parpar.exe --version"))

It runs as expected for me. Does it for you? If so, please share the script that causes the above error. If not, do you happen to have something in your environment/config that would trigger Node's inspector to run?

[ayniin]

The script:
`import subprocess
import os

dir_path = os.path.dirname(os.path.realpath(file))
parpar_path = os.path.join(dir_path,'parpar.exe')
os.system(parpar_path)
subprocess.call([parpar_path])`

I tryed it on 3 different windows installations always the same result. Two were vms and was a fresh install from windows.

Okay found the Problem i only get the error when i try to run it from vscode.

[animetosho]

Can you get the environment from VSCode? Probably use a command like Get-ChildItem env:* - in the output, see if there's node options or anything related to 'inspect'.

[ayniin]

i Found these:
VSCODE_INSPECTOR_OPTIONS: :::{"inspectorIpc":"\\\\.\\pipe\\node-cdp.26080-191dd023-0.sock.deferred","deferredMode":true,"waitForDebugger":"","execPath":"C:\\Program Files\\nodejs\\node.exe","onlyEntrypoint":false,"autoAttachMode":"smart","aaPatterns":["y:/#Programming/BAKA_EZPZ_MIGRATION/**","!**/node_modules/**","**/$KNOWN_TOOLS$/**"]}

[animetosho]

Hmm, I don't think that's it unfortunately.
If you figure how to reproduce the issue outside of VSCode, let me know.