Re: [Py2exe-users] Determine why module is included?

[Grant E. <gr...@vi...>]

On 2007-04-16, Andrea Gavana <and...@gm...> wrote:
> Hi Grant,
>
> On 4/16/07, Grant Edwards wrote:
>> On 2007-04-16, Larry Bates <lar...@we...> wrote:
>>
>> >> I can't figure out how to determine why a particular module is
>> >> being included by py2exe.
>> >>
>> >> In my case, I'm bundling a wx app, and py2exe thinks tcl and
>> >> tk need to go along with it -- I'd like to find out why.
>> >
>> > Are you using PIL?
>>
>> No.
>>
>> > It includes them but doesn't need them unless you use the
>> > viewer.  I normally exclude them with:
>> >
>> > "dll_excludes": ["tcl84.dll", "tk84.dll"]
>>
>> Yup, I know how to exclude them.  What I can't figure out is
>> how to determine why a particular module is included.
>
> Everything (o almost everything) is done by the modulefinder in
> py2exe: it basically scans the source code to look for import
> statements and determines the module dependencies. What you could do,
> is to use the following flag when compiling:
>
> python Setup.py py2exe --xref

Coo, that's exactly what I was looking for.  I never realized
there were command-line options (now that I know that, --help
provides a nice summary).

-- 
Grant Edwards                   grante             Yow! When you get your
                                  at               PH.D. will you get able to
                               visi.com            work at BURGER KING?