In the last few days I have begun to understand pyinstaller. Depending on the generate_folder switch, launchLeo.spec now generates either:
1. a single file, Leo.exe, containing *everything* needed for Leo, or, 2. a folder containing Leo.exe and everything else needed. The advantage of 1 is that the user can just double-click on it to start running Leo. The advantage 2 is that the user can see and open .leo and .py files that are part of Leo. In the next day or so I'll be making both versions available for newbies. Either way, the user need install *nothing* to run Leo! Imo, both PyInstaller itself and its documentation are superb. However, I really didn't understand what was going on until I started using PyInstaller. The key Aha was that, *even in case 2*, so-called pure python modules do *not *appear in a leo folder. Instead they are put somewhere else, probably in Leo.exe itself. Indeed, to get any leo folder at all, files must be added to the so-called "datas" list. At present, the same datas list is used in both case 1 and case 2, but there is no point in adding most of those elements for case 1 because there appears to be no way to open those files. This is going to be a big deal for Leo. For the first time ever, people will be able to try Leo without installing anything. This what Kent has been wanting forever, and I now see much more clearly why. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
