[wingide-users] Debugging a Python executable (py2exe)

Tony Cappellini cappy2112 at gmail.com
Tue May 6 17:27:13 MDT 2008


There seems to be a typo in the Wing docs- regarding py2exe

EXTRA_PYTHONPATH=\Python25\Lib\site-packages\py2exe\samples\simple\dist

Why does the sample directory need to be in EXTRA_PYTHONPATH?
There is no dist directory under
\site-packages\py2exe\samples\simple\



On Tue, May 6, 2008 at 3:39 PM, Max Slimmer <max at theslimmers.net> wrote:

> I have a fairly complex app that I build with py2exe, however I test it in
> the Raw so to speak, My debuging and testing is mostly done before running
> py2exe, I leave that for final build and packjaging step when I know it all
>  works.  When I run the packaged app and there is an error which produces
> traceback it usually refers to pyc files.
> max
>
> Tony Cappellini wrote:
>
> >
> >
> > Has anyone tried debugging a py2exe executable with Wing?
> > I've followed the steps in the Wing manual, but Wing never hits the
> > breakpoint I've set- and and never switches to "debug mode".
> >
> > I'm running the program from the command line, have kEmbedded=1, and
> > have active listening set.
> >
> > I don't suppose there is a way to run the executable (instead of the
> > .exe) - by pressing F5....?
> >
> >
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _________________________________________________
> > Wing IDE users list
> > http://wingware.com/lists/wingide
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/wingide-users/attachments/20080506/8c2244ea/attachment.html


More information about the wingide-users mailing list