MMM-PythonPrint customisation

RobCee

@sdetweil I am using python3 and I have updated the two references to ‘python’ -> ‘python3’ to reflect this

sdetweil

@RobCee right, you don’t have to change the code, just use the config.js setting

{ 
module:
     config: {  
         pythonName:'python3',
    }
}

RobCee

@sdetweil ok, I will try it there then and see what happens.
Tracking down errors in this MM OS is fun…

sdetweil

@RobCee o, I see that I have a potential bug… if the command: is not configured,
it defaults to “”… oops…

I just pushed an update got that

git pull in the module folder

to debug

add debug: true

and then look where u start MM… (this doing npm start )

[11.04.2022 10:55.13.087] [LOG]   MMM-PythonPrint received a socket notification: CONFIG - Payload: [object Object]
[11.04.2022 10:55.13.087] [LOG]   PythonPrint spawning modules/MMM-PythonPrint/printit.py
.
.
.
.
[11.04.2022 10:55.18.114] [LOG]   PythonPrint sending program output=hello

RobCee

@sdetweil I will have a go with that, but I think I have a slightly different problem of my own making.

sdetweil

@RobCee ok, I also fixed the use of the pythonName and added it to the debug message

[11.04.2022 11:04.20.218] [LOG]   PythonPrint spawning modules/MMM-PythonPrint/printit.py using python3
.
.
.
.
[11.04.2022 11:04.25.244] [LOG]   PythonPrint sending program output=hello

RobCee

I’m not sure why, as I did manage to get it working at one point, but I think the issue is that I am using the MM OS Docker image to run all this.
I think this means that the path expectations are different from the assumptions that I am making.
I may have to give in and just build the whole thing manually - it will probably be quicker than trying to fault find the install, given it’s obfuscation.

sdetweil

@RobCee yes, docker paths and if OUTSIDE the MM tree, then YOU have to add new volume statements to the docker setup to map them

RobCee

@sdetweil yeah, I am deliberately keeping all the module paths in the default place, but it still doesn’t like it.
But if I go into the docker container, it doesn’t seem to have access to Python, so maybe that’s the problem.
It is all rather confusing. (More so from your end, no doubt)

sdetweil

@RobCee this.file(filename) will prepend the file system path to the module folder

I just pushed a fix to do the same in the module, instead of the __dirname prefix