Hi, Martin!!

Thanks for pointing out this annoying bug!!
I'd like to bring you a new version v1.1.

What was happening. The path to Python was hardcoded into the script—the one on my machine.
Apparently, your Python is installed elsewhere, so there was nothing to run.

What's happening now? The first time you try it, the script tries py.exe, C:\Windows\py.exe, python.exe, python3.exe, and python,
and remembers the one that responded. The check is cheap — Python responds before it starts loading numpy, so it passes even if the libraries aren't there yet.

Error messages are now different, not just one for all cases.
If Python isn't found, it says it was looking for it and suggests adding it to the PATH.
If it's found, but the calculation fails, it says the problem is most likely with the libraries and suggests pip install numpy pillow.

To check, simply run the command: if Python is found, the error will disappear on its own.

Enjoy!