On Sep 6, 7:18 am, "Edward K. Ream" <[email protected]> wrote:
> The weirdest thing of all. I just changed console_python.py, but the > modification date of the file didn't change!!!!! Reloading the file > verifies that its contents *did* change. > > This would explain a lot ;-) Mystery partially solved. I checked the disk for errors. There were none. I have finally been able to change the file. To do this, I moved the file out of the blender tree entirely(!!) Amazingly, what I saw was the *unchanged* (original) file. I changed the file outside the blender tree, then moved the file back into the blender tree. Now the change "took". What I don't understand is where the new versions were stored!!! This may be some kind of deep Windows mystery, possibly abetted by Blenders caching mechanisms. Anyway, I can now add something to the blender signon, which means, presumably, that I can patch any blender Python code. Hooray. Note that there was a longish delay on blender startup after the change, but later startups went very quickly. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
