On Jun 29, 2006, at 10:43 PM, Phillip J. Eby wrote:
At 04:13 PM 6/29/2006 +0100, Paul Moore wrote:
Agreed. But in the absence of a standard, supporting package authors' existing approaches, which work with other distutils mechanisms, seems like a reasonable requirement.
Anything that the package author installs as package data, or using the data_files option to setup(), is included in the egg. And if you install unzipped, you should be able to browse the included docs.
Installation of anything but python modules and the data they need to function seems to be outside of the scope of eggs. There's nothing wrong with that, but just means that there is room for something beyond eggs.
As an example why "stuff everything in an egg" can't work for everything, PyObjC uses bdist_mpkg to create an installer that also installs additional templates for Xcode, those cannot be part of an egg because the egg will not be in a location where Xcode will look for templates.
AFAIK some future version of bdist_mpkg will install python packages as eggs, while still allowing installation of other stuff.