https://bugs.kde.org/show_bug.cgi?id=391508
--- Comment #1 from Fredrik Averpil <[email protected]> --- I just had a quick look at the code in plugins/pykrita/kritarunner/plugin/utilities.cpp. In Python::setPath I can see that PYTHONPATH is not being merged into Krita's search paths on Windows and in some scenarios, it is being skipped on macOS/Linux too... I'd say either _always_ merge PYTHONPATH into the search paths or _never_ do it. The latter probably being a wise choice avoid future problems (which usually turns up when users start putting stuff in their PYTHONPATH). Regardless, I want to re-iterate on that I would prefer to specify a script filepath to kritarunner. This would not only add simplicity to kritarunner, but also offer the possibility to tailor to the user's need in terms of the script's location. After having given all of this some thought, it would also be good to be able to define arguments or the function name to execute (with arguments to the function). -- You are receiving this mail because: You are watching all bug changes.
