I thought this happened to me before... definitely this morning:
I'm now used to the new location for my Python scripts (Python2-includes). I tried modifying one today, and then used the "Reload Libraries and Attachments" menu command to try out the new version.. I saw in Indigo's log that the menu command executed. I then modified the script again, and then tried the "Reload Libraries and Attachments" menu command again, but this time the log didn't show any reloading activity, and my script modifications were not in effect. I tried the menu command several times, both from a computer running Indigo as a client, and again from the computer on which the Indigo server is running.. Then I tried restarting the server, with and without quitting the Indigo client(s). Indigo continues to use the version of the script prior to me modifying it!
What is happening? Is this a bug? Why did I see log confirmation of the Reload the first time, but not subsequent times, even after restarting Indigo? Do I not use "Reload Libraries and Attachments" after modifying a script to get Indigo to use the new version? Are scripts cached somewhere? (PS: I really hate MacOS caching, which regularly finds ways to really mess me up, but I digress.)
How does one get Indigo to honor a modified script?
I didn't restart the computer, and don't want to (shouldn't have to). Running MacOS 10.14.6, Indigo 7.4.1. There are no files in either of the Scripts folders, so it's not an issue of Indigo using the wrong script file.