On Fri, Nov 21, 2014 at 8:10 AM, Edward K. Ream <[email protected]> wrote:
> > > On Wed, Nov 19, 2014 at 8:55 PM, Davy Cottet <[email protected]> > wrote: > >> So `sudo python setup.py install` issued no errors, but attempting to run >>> Leo afterwards does? >> >> > Yes. I see this as well. Anyone have any ideas how to fix that? > Are we sure this really is a problem? From: http://stackoverflow.com/questions/2604600/why-does-easy-install-extract-some-python-eggs-and-not-others QQQ If the package contains only pure-Python code, it can stay as just an egg file. The Python interpreter can load the Python modules directly from the egg. If the package contains modules written in C or other data, then egg needs to be extracted so the C modules and/or data can be accessed. That's the default behavior of packages, I believe. Newer versions of Python might be able to load C modules from egg files; I'm not sure about that part. The creator of the package can also specifically instruct the installer to unzip the package, by passing zip_safe = False to setup() in their setup.py. QQQ So why not just set zip_safe = False and be done with it? 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.
