Re: [Py2exe-users] py2exe and win32com shell or UTF 8 encoding

[Zeno <ger...@gm...>]

Mark Hammond <skippy.hammond <at> gmail.com> writes:
> 
> Have you tried reverting the changes and see if they go away?  Then just 
> one at a time to see which one is the problem?  Or even seeing if the 
> problem exists without py2exe to help tell you if you are asking in the 
> correct place?  FWIW, if you do (1), you get what you deserve - or at 
> least need to know what you are doing well enough that you understand 
> what you get ;)
> 
> Cheers,
> 
> Mark
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> 

Hi Mark,

Thanks for the response. Yes, I have done as you suggested. Or rather, I tried
moving the shell include files from the exe directory and it then crashes and
writes the "atexit" exe log which I was expecting. When I replace the shell
files the application starts appropriately. When I run into my next crash ( an
unrelated bug ) the "atexit" log is not generated and the pop-up message is not
displayed.

This unrelated bug does not happen when I am running the app as a python script
so I am unable to replicate it except with my py2exe executable. Thus, this
debug output is a sticking point.

Thanks again. Best,

-Zeno

PS - the long and short of this is that the problem is with importing shell, not
the UTF-8 encoding.