On Jul 12, 2005, at 5:18 PM, Kevin Dangoor wrote:
On 7/12/05, Bob Ippolito email@example.com wrote:
The most expedient option would be to specify the eggs and a pth as resources (or data_files) manually.
Second to that, you could make sure all the eggs are unzipped and on sys.path when the setup.py is running (this doesn't solve the resources thing, but modulegraph doesn't do that anyway).
As far as fixing the implementation, I don't know.. I don't really have time to work on open source Python stuff right now. Patches accepted, of course.
That's why I was asking about complexity... I'm considering digging in myself, but I haven't touched py2app's code before.
I really don't know, I haven't looked at the code recently, especially the modulegraph stuff.
I was all in favor of the most expedient option that you mention above. However, the problem that I ran into was that standard library modules that were needed by the eggs weren't getting picked up (since the eggs were just "data files"). If there is an easy way to run modulegraph on the eggs, then maybe a short-term solution is:
Well, just do the second suggestion then. "Install" the eggs somewhere, unzipped, and make sure it's on sys.path during setup.py. Maybe you could crank the ez_setup wheels (or whatever module is appropriate, I haven't looked at eggs yet) at the top of your setup.py and automate this.