Read the statement by Michael Teeuw here.
MMM-PythonPrint customisation
-
@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 -
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. -
@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
-
@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) -
@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
-
@sdetweil But if I exec into a bash console in 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) -
@RobCee you had to install python in the container if it wasn’t as part of the instance
-
@sdetweil I have just had that lightbulb switch on in my head…
-
@RobCee i don’t think the image has python installed
-
@sdetweil you are correct. It doesn’t have python installed with it.
My next challenge is to work out how to get that up and running.Once I have it running I will get back to you on your module.
