[Distutils] py2exe and eggs

[Jay Parlar]

On 8/19/05, Phillip J. Eby <pje at telecommunity.com> wrote:
> I guess I'll add it to my list to see if I can create a py2exe wrapper for
> setuptools.  Or, since Thomas is now playing with setuptools also, perhaps
> he, Kevin, and I can work something out to make py2exe work as a setuptools
> extension.  Since setuptools provides hooks for such extensions to add
> setup() keywords and new commands, maybe we can get py2exe hooked in such
> that it just adds the required eggs to the zipfile in "basket" mode, and
> doesn't bother tracking imports to packages found in eggs.  (Except maybe
> for pkg_resources, which it should just always include in the zipfile.)

Well, the issue I just ran into was that the 'symbol' package wasn't 
being brought in by py2exe, because the only place it was imported was
in RuleDispatch (or maybe PyProtocols, can't remember).

So there'd still have to be some kind of import tracking done by
py2exe (or setuptools), because when you're running with py2exe, you
can't expect the entire stdlib to be available.

> You can build a bdist_wininst from a source checkout, and then run the
> generated Windows installer.  Or you can use individual commands like
> install_lib, install_data, install_scripts, and so on.  Setuptools doesn't
> modify those commands, so they still have the ability to do non-egg installs.

Didn't even think of that, thanks for the suggestion.


Thanks,
Jay P.