Hey there,
Lex Trotman via Users wrote:
The question is why does the python compile work but not the execute?
Did the OP change compile but not change the execute for some reason?
Or is there an issue of PATH due to the different ways compile commands and execute commands are run.
No idea on any of those, especially since I had no idea that Python could even be compiled.
And anyway, why did the distro packager not use --with-python-command=... when building the package so it will work for their users (Geany 1.38 or later but the OP didn't say what version they had)?
ahh well [end rant]
Interesting. I didn't realize they could. You'd think they would have realized it and done exactly that. It wouldn't surprise me if it's because they have so many thousands of programs that they take a hands-off approach when it comes to packaging.
Anyway, my apologies for jumping in on this thread when I did. I had only received the OP's message when I sent my reply. It wasn't until later that the rest of the messages came in even though they were time-stamped earlier than mine and the problem had already been solved. It's one of those occasional internet burps, I suppose, but my intentions were good.
A nice side-effect of this for me was that I poked around in the Build menu and ended up messing around with and customizing the Lint command. I'm loving the way that Geany highlights an offending line if you click on it in the "Compiler" panel. It's simply glorious. This program just gets better and better and better the more you use it.