On Fri, Nov 7, 2014 at 5:58 AM, Edward K. Ream <[email protected]> wrote:
> This is the same weird behavior I see when installing of Python 3.4. To debug this problem, I did the following:: 1. Right-clicked the Leo icon and chose properties. 2. Changed the "target" from pythonw.exe to python.exe so that Leo run in a console. 3. Saved the changes to the properties. 4. Double-clicked the icon. Imagine my surprise when Leo loaded correctly!! This is absolutely bizarre. Afaik, there should be absolutely *no* difference between pythonw.exe and python.exe, but apparently on Python 3.x there is. My *guess* is that some part of startup is failing on 3.x, and failing in such a way that Leo *kinda* starts up, but not well. This is top priority right now. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
