About one month ago or so my Dr. Python compiler (interpreter) died. I had closed Dr. Python to go and eat dinner then came back to re-open and continued where I had stopped and... nothing. This came at a terrible time as I was in the middle of some very important code testing. I tried everything I could think of but did not have time to fix it nor was I sure how to. I opened IDLE and plugged away. IDLE worked, yes, but what I can say about it save for that it's better than nothing I guess. :-|
Python Mod vegaseat encouraged me to fix Dr. Python-- make it work. I tried, but gave up as I could not get any response. I was confused as to these errors so I continued with IDLE.
Today though, I thought I would give it one more try; I downloaded the latest version from SourceForge, unzipped it, and tried to run it. How I got it to open and work all centered around how it opened and with what program-- I will spare the details, but I think it has something to do with some sort of file and\or memory corruptions on my system. I opened it manually and it worked! I was so relieved. :cheesy:
The reason I am posting this is to encouarage other Python programmers to try Dr. Python if they have not yet. Dr. Python is:
- efficient and stable
- has a clean and simple (but not overly-simple) GUI
My production levels rise noticeably by using Dr. Python.