Nate Lowrie wrote: > On Fri, Mar 6, 2009 at 10:33 AM, Paul McNett <[email protected]> wrote: >> Roger Lovelock wrote: >>> Perhaps I am a victim of the past, but the size of the files created by >>> py2exe are really scary to me. I know we have a lot more resources these >>> days - but I was brought up in the days every k counted! >>> Have read about using UPX and other tools on the output from py2exe. Is this >>> a good idea? or even worthwhile? any other approaches? >>> My application seems to be bigger when packaged with py2exe than if I >>> shipped the dabo runtime plus my code! >> It's mostly wxPython that accounts for the file size. I was initially >> shocked, too, >> but in practice it really is no big deal. FWIW my INNOSetup-generated >> setup.exe is >> usually around 13 MB. Just wait until you start building on Mac, where the >> equivalent >> setup.dmg will be about 21 MB. > > You should find it to be able 1/4 MB smaller now. I moved the card > images out of the framework and into the demo, eliminating some > uneeded resources.
That's a good change, IMO, but it won't reduce *my* exe size as my setup.py already excluded the card images... also I believe this is in the appwizard-generated setup.py as well. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
