problem with gadfly and py2exe

[Max]

"Andy Todd" <andy47 at halfcooked.com> ha scritto nel messaggio
news:Xns9214724F891FAandy47halfcookedcom at 203.109.252.31...
> "Max" <nospam at nospam.nospam> wrote in news:9eJF8.69521$zW3.1064537
> @news1.tin.it:
>
[...]
> > I had a similar problem using my module in the beginning, because py2exe
> > could'nt find the shelve module by itself. I solved the problem for my
[...]
> > Has anybody experienced the same problem or has any idea of  which
> modules
> > gadfly relies upon (and i might try to force import of in py2exe) ?
[...]
> Err, I'm not an expert but I think the problem is in the chain of module
> imports that you trigger with "import gadfly". This will actually import a
> module which in turn relies on other modules which in turn rely on other
> modules, etc. As far as I'm aware py2exe isn't psychic and only knows what
> to package based on any "import" statements in your code.
>

Exactly what i supposed... infact i had a similar problem with a written by
myself doin' part of the functions of gadfly, but in that module i traced my
imports. Doing the same in gadfly implies  the study of the gadfly project
(i just started using it), so i asked if anybody already has a solution, or
the list of modules gadfly relies upon... to trace the import chain...

> To the best of my knowledge gadfly doesn't rely on any external objects
> (apart from Python of course) but you will probably need a way to tell
> py2exe that it should package the whole package and not just the file that
> you explicitly import (which is actually called database.py I think, but
> lets not go there).
>

What i did to solve "previous release of my problem"... :)

> Sorry I can't be more specific but hopefully this gives you something to
go
> on with.
>

Thanks anyway,
Max