Giovanni, have you given any more thought to how the egg analysis info should be applied, concretely?
Arve On Mar 12, 11:05 pm, [EMAIL PROTECTED] wrote: > On Mar 11, 3:36 am, Giovanni Bajo <[EMAIL PROTECTED]> wrote: > > > On Mon, 2008-03-10 at 14:44 -0700, [EMAIL PROTECTED] wrote: > > > I've found out how to determine which eggs should be included, by > > > mapping from Python modules. > > > I'm not sure I understand. Would you please elaborate? > > What I mean is that I detect which eggs Python modules belong to. > > > > The question now is at which point this > > > information should be utilized, and how egg metadata should be > > > included. Should the eggs simply be deduced when the CArchive is > > > created? > > > No, I think this belongs to the Analyze() function of the spec file; you > > should put the information about the .egg that are needed among the > > results of Analyze. > > Won't this approach lead to increased complexity from the client's > point of view though? Already one has to refer to the results of the > analysis (pure, scripts etc.) directly, eggs would be yet another > variable as far as I can tell. > > > > What I'm thinking with regard to egg inclusion is that all egg > > > metadata should be added to the CArchive, perhaps beneath a directory > > > "eggs/" to avoid clashing with other archive entries. Then this > > > metadata can be extracted in order to bootstrap pkg_resources, when > > > the time comes. > > > Why can't they go within EGG-INFO directory within each package, > > reflecting the exact structure they have in an .egg directory? If the > > analyze phase deduces the egg information as "DATA" files in the TOCs, > > they would be automatically added to the PYZ Archive (*not* the > > CArchive), if I'm correct. > > EGG-INFO directories are not placed _within_ packages though? They are > normally in the .egg directory, which may also contain a Python > package. I don't think we should treat EGG-INFO as any data though; > more responsibility than necessary is placed in the hands of the > client, i.e., one has to ensure a certain structure in the > distribution directory. > > Arve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
