I had to change a .wxg file by creating an additional panel. I had to modify some pre-existing py files to accommodate the new panel’s addition.
On the CLI, when I run the program, it runs just fine but when I create an exe using PyInstaller-2.0, the exe crashes. It appears and disappears from Windows Task Manager,
I used AppCrashView to see what happened and it said that “Python.exe has stopped working”
When I added the new panel, I had no new module imports… I re-installed WxPython 2.8.12.1, Python 2.7.2 but that didnt help.
Instead of adding a new panel with content, I added a blank panel just for the heck of it to see if that worked… that didnt work either.
I had to change a .wxg file by creating an additional panel. I had to
modify some pre-existing py files to accommodate the new panel's addition.
On the CLI, when I run the program, it runs just fine but when I create
an exe using PyInstaller-2.0, the exe crashes. It appears and disappears
from Windows Task Manager,
I used AppCrashView to see what happened and it said that "Python.exe
has stopped working"
When I added the new panel, I had no new module imports.. I re-installed
WxPython 2.8.12.1, Python 2.7.2 but that didnt help.
Instead of adding a new panel with content, I added a blank panel just
for the heck of it to see if that worked.. that didnt work either.
I am not sure what I have landed on..
has anyone else seen this before?
Are you sure you have all the same versions of everything that you had when you made the .exe the last time? If you remove all your recent modifications and try to build the .exe again does it work? If not then something besides adding the panel is causing the problem. If you make a simple application with just a wx.App and a wx.Frame and convert that to a .exe does that work? If so then slowly migrate that from the simple app to the real app and see when it stops working. If not then take a closer look at your tools and how you are using PyInstaller.
I had to change a .wxg file by creating an additional panel. I had to
modify some pre-existing py files to accommodate the new panel’s addition.
On the CLI, when I run the program, it runs just fine but when I create
an exe using PyInstaller-2.0, the exe crashes. It appears and disappears
from Windows Task Manager,
I used AppCrashView to see what happened and it said that "Python.exe
has stopped working"
When I added the new panel, I had no new module imports… I re-installed
WxPython 2.8.12.1, Python 2.7.2 but that didnt help.
Instead of adding a new panel with content, I added a blank panel just
for the heck of it to see if that worked… that didnt work either.
I am not sure what I have landed on…
has anyone else seen this before?
Are you sure you have all the same versions of everything that you had
when you made the .exe the last time?
//Yes. 100%
If you remove all your recent
modifications and try to build the .exe again does it work?
//Yes, it does works fine on exe if I roll back my changes - which is just that 1 additional panel on the existing .wxg file.
If not then
something besides adding the panel is causing the problem.
If you make
a simple application with just a wx.App and a wx.Frame and convert that
to a .exe does that work?
//On the same .wxg, I replaced the “new panel” that I wanted to add with a “blank panel”. That worked in development mode but that also failed in the exe mode. (exe would not even launch - appears and disappears from the task bar)
If so then slowly migrate that from the
simple app to the real app and see when it stops working. If not then
take a closer look at your tools and how you are using PyInstaller.
//Had I updated a tool, that might push me to think something is not compatible but I did not think adding a panel would lead to something funny…
···
On Saturday, July 20, 2013 7:24:09 PM UTC-7, Robin Dunn wrote:
…
With PyInstaller can you create a “console” exe like one can with
py2exe? If yes do this and try to run it, you might see some
traceback which is otherwise not showing.
Werner
···
Hi,
On 22/07/2013 03:04, kb wrote:
If you
make
a simple application with just a wx.App and a wx.Frame and
convert that
to a .exe does that work?
//On the same .wxg, I replaced the "new panel" that I wanted to
add with a “blank panel”. That worked in development mode but
that also failed in the exe mode. (exe would not even launch -
appears and disappears from the task bar)
If you make
a simple application with just a wx.App and a wx.Frame and convert that
to a .exe does that work?
//On the same .wxg, I replaced the "new panel" that I wanted to add with
a "blank panel". That worked in development mode but that also failed in
the exe mode. (exe would not even launch - appears and disappears from
the task bar)
That doesn't really answer my question, but whatever. Here are some more.
What is the content of the new panel? How and where are you adding it? Do you do anything with it in the Python (non-wxGlade) code? Can you duplicate the problem in a small application written by hand (no wxGlade)? If so then please share it. All we can do is guess until you give us a concrete example to experiment with.
This has been resolved. The path was the problem. It had to be a silly issue which is why it took so long… i guess! and I found the “-c” console option on pyinstaller to be very helpful. I was using -w option where the console is suppressed - but that’s how its meant to work for my case. But -c option is very helpful while debugging!
···
On Friday, July 19, 2013 6:36:52 PM UTC-7, kb wrote:
Hi There:
I had to change a .wxg file by creating an additional panel. I had to modify some pre-existing py files to accommodate the new panel’s addition.
On the CLI, when I run the program, it runs just fine but when I create an exe using PyInstaller-2.0, the exe crashes. It appears and disappears from Windows Task Manager,
I used AppCrashView to see what happened and it said that “Python.exe has stopped working”
When I added the new panel, I had no new module imports… I re-installed WxPython 2.8.12.1, Python 2.7.2 but that didnt help.
Instead of adding a new panel with content, I added a blank panel just for the heck of it to see if that worked… that didnt work either.