David Brown wrote:
Is there a known problem using py2exe on programs that have a py.shell.Shell
window? I have been using a py.shell.Shell window as a debugging aid in a
program, but when it came to building an exe file and installer, the program
simply would not run (no error messages or anything) while the shell was
there. After commenting out the "from wx import py" and the actual
py.shell.Shell creation code, it worked perfectly. It's not essential that
the shell is included in the exe file (whereas it *was* essential that the
program was finished and installable today!), but I'm curious as to what
went wrong.
May I suggest to try psiShell ?
I never had problem to build exe file with py2exe
http://www.chez.com/spinecho/pypsi/pagpypsi.htm
The file psi-53-py23-source.zip contains a Python shell for
wxPython. There is also a demo module MultiPsi.py showing
two (!) python shells on the same wxFrame.
Jean-Michel Fauth, Switzerland
"Jean-Michel Fauth" <jmfauth@bluewin.ch> wrote in message
news:001101c3aa12$d36746c0$2f99ca3e@famille...
David Brown wrote:
> Is there a known problem using py2exe on programs that have a
py.shell.Shell
> window? I have been using a py.shell.Shell window as a debugging aid in
a
> program, but when it came to building an exe file and installer, the
program
> simply would not run (no error messages or anything) while the shell was
> there. After commenting out the "from wx import py" and the actual
> py.shell.Shell creation code, it worked perfectly. It's not essential
that
> the shell is included in the exe file (whereas it *was* essential that
the
> program was finished and installable today!), but I'm curious as to what
> went wrong.
May I suggest to try psiShell ?
You may indeed suggest it - I've downloaded it (while I've got the link
handy), and will have a look when I get the chance. What sort of licence
does it have? I didn't notice any information on your site. At the moment,
the program in question is simply for testing an embedded system, and the
customer has got a copy of all the source code in the program, but for the
future, I would need to know that I could release a program using it as
closed source. If it uses the standard Python licence, then that is great.
David
ยทยทยท
I never had problem to build exe file with py2exe
http://www.chez.com/spinecho/pypsi/pagpypsi.htm
The file psi-53-py23-source.zip contains a Python shell for
wxPython. There is also a demo module MultiPsi.py showing
two (!) python shells on the same wxFrame.
Jean-Michel Fauth, Switzerland
program, but when it came to building an exe file and installer, the program
simply would not run (no error messages or anything) while the shell was
there.
Did you try building the py2exe as a console application? I had a similar
issue and it was because py2exe wasn't picking up one of my imports (the
import was based on a text string, so it wouldn't have been able to pick
it up ever anyway).
Running with py2exe -w showed nothing happening. With py2exe -c I got a
nice stack trace of the failed import.
Roger
"Roger Binns" <rogerb@rogerbinns.com> wrote in message
news:00ea01c3aa87$78aaeb40$3501a8c0@rogersqyvr14d3...
>>> program, but when it came to building an exe file and installer, the
program
>>> simply would not run (no error messages or anything) while the shell
was
>>> there.
Did you try building the py2exe as a console application? I had a similar
issue and it was because py2exe wasn't picking up one of my imports (the
import was based on a text string, so it wouldn't have been able to pick
it up ever anyway).
Running with py2exe -w showed nothing happening. With py2exe -c I got a
nice stack trace of the failed import.
Roger
That's a useful hint - it seems that importing the module "DataStructures"
fails. I'm not too worried about missing pyShell on this occassion - after
all, if the end user wants shell access, they can just install python and
run the program directly. But I like to know what's going on, and what's
going wrong, for future reference when it might be important. With the
output from the "py2exe -c" version, I expect I could now fix the problem
with forcably including the DataStructures module in the exe file (and then
repeating the process if other imports fail). It's certainly a useful trick
to remember in the case of other future problems.
David
With the
output from the "py2exe -c" version, I expect I could now fix the problem
with forcably including the DataStructures module in the exe file (and then
repeating the process if other imports fail).
Just add -i and a comma seperated list of modules to the py2exe command line.
I was doing this just today 
Roger