On Thursday, February 25, 2016 at 7:38:36 AM UTC-5, Edward K. Ream wrote: > > I recently had an Aha about releases: minor bugs don't matter! Leo's > latest code is typically more stable than any previous "final" release, so > we should release "final" releases much more often. Say every two months or > so. > > Regular releases are important. Some people will only download so-called > "final" releases. And they keep Leo in the public eye. > > The remaining tasks before Leo 5.1.1 final are: > > - Get PyInstaller versions of Leo working on Windows, Linux & MacOS. > - Fix problems with the vim and xemacs plugins. > - Polish the Code Academy posts. > This is the best news about Leo that I have read in some time. It arrives as I was preparing to write you to ask for detailed instructions for rolling my own PyInstaller versions for Windows and OS X.
I expect that I am a minority among the community of Leo users, because following the Leo documentation and using full-blown installations of CPython, Qt and Leo isn't an option for me on Windows 7 or on OS X. I have to leave IronPython as the default Python on my Windows machine because it is the scripting engine for applications I user for work, and I don't have source code for those or the ability to configure them to ignore a secondary Python. I log in without Admin rights to the Mac I use, and I have multiple log-ins, which means that Homebrew is not useful. -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
