* Danek Duvall <danek.duvall at sun.com> [2008-11-25 16:05]: > On Mon, Nov 24, 2008 at 04:27:10PM -0600, Brian Cameron wrote: > > > Not true. Such egg files are a result of building a module via Python > > setuptools. This is discussed in the setuptools ARC case: > > > > http://sac.sfbay/PSARC/2008/084/proposal.txt > > That case doesn't propose that the files be shipped in the binary product, > though, and given that the files appear to be useful only on the > development and building side of the distribution, it's not clear to me why > they should be shipped, never mind exported as interfaces. > > > - CSSutils (LSARC 2008/658) > > - Twisted-Python 8.1 and Twisted-Python-Web2 8.1 (PSARC 2008/670) > > - Elisa (LSARC 2008/713) > > The mysql and zope extensions also seem to be shipping the egg files.
Ignoring the bugs in the mysql extension, I would like to understand why egg files are an appropriate delivery mechanism for us as distributor/OS vendor. Eggs seem to be more opaque than unpacked module deliveries, and appear to have performance overhead (from the unpacking, although there may be caching options I've not found). If there isn't a strong argument, I think we should insist on unpacked delivery. - Stephen -- sch at sun.com http://blogs.sun.com/sch/
