Full Path to .py script fails

[isa56k]

I'm using the following to call my python script:

var PythonShell = require('python-shell');
var pyshell = new PythonShell.run('/home/pi/Development/Sensor/python/SenseHat.py');

// get message back
pyshell.on('message', function (message) {
  // received a message sent from the Python script (a simple "print" statement) 
  console.log(message);
});

// end the input stream and allow the process to exit 
pyshell.end(function (err) {
  if (err) throw err;
  console.log('exit');
});

If I use the full path to the script it fails with the error below:

/home/pi/Development/Sensor/node/pythonTest.js:14
  if (err) throw err;
           ^
Error: python: can't open file 'home/pi/Development/Sensor/python/SenseHat.py': [Errno 2] No such file or directory

    at PythonShell.parseError (/home/pi/node_modules/python-shell/index.js:190:17)
    at terminateIfNeeded (/home/pi/node_modules/python-shell/index.js:98:28)
    at Socket.<anonymous> (/home/pi/node_modules/python-shell/index.js:78:9)
    at emitNone (events.js:72:20)
    at Socket.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:903:12)
    at doNTCallback2 (node.js:439:9)
    at process._tickCallback (node.js:353:17)

If I use the following path to the script it all works ok:
../python/SenseHat.py
and so does:
../../../../../home/pi/Development/Sensor/python/SenseHat.py

[extrabacon]

It'a a bug, absolute paths are not supported because of the handling of the scriptPath option (https://github.com/extrabacon/python-shell/blob/master/index.js#L53).

Quick workaround: set scriptPath option to directory containing your script (/home/pi/Development/Sensor/python), then run the script (SenseHat.py). This way the full path to the script will be built correctly.

[isa56k]

var pyshell = new PythonShell.run('SenseHat.py', { scriptPath: '/home/pi/Development/Sensor/python/' } );

That works, sorry... didn't see that option!

[extrabacon]

It's still a workaround, python-shell should support absolute paths. Reopening so I can fix this in a future release.

[phtdacosta]

Just to know, is it fixed yet? Thanks

[maziarz]

Heres a workaroun for OSX. I recommmend using os lib to determine the OS (darwin, win32, etc.)

import path from 'path'

const somePath = '/some/path/here/script.py'
let fileName = path.dirname(somePath)
let filePath = path.basename(somePath)

PythonShell.run(fileName, { scriptPath: filePath }, function (err, results) {
    ...
})

[jzombie]

Just to know, is it fixed yet? Thanks.

(says it is closed; issue is not fixed for me)

[Almenon]

? The issue is still open - for now just use the workaround

[Trevirirus]

the workaround is not always working:

pyshell = new pyShell('main.py',{scriptPath: path.join(__dirname, '..', 'src', 'GNSS_Positioning')} , options)

also the scriptpath inside the options is resulting in the above described errors.

please support full paths

[Almenon]

@KarthikSamaganam4 this is unrelated to this issue - I've opened a new issue for you. See #151

[Almenon]

PythonShell should support both relative and absolute paths now. For example, the runString function works by passing an absolute path to the a file in the temp directory over to pythonshell. The function is unit tested in both windows and mac so it will work no matter the platform.

@Trevirirus, can you double check if it has been fixed in the latest version (1.0.4) of python-shell please? You should be able to pass the path into pythonshell without having to specify any options.

@extrabacon, I fixed it in 4ba8b5e by removing the ./ which was causing an error with absolute paths on mac. Was there any reason ./ was in there in the first place? Hopefully I didn't break some weird edge case not covered in the unit tests.