Ok, so GUI2exe just won't work on my computer (keeps crashing). So I tried to run PyInstaller directly. I followed the instructions, and it actually does make the executable as I ask, but that executable simply segfaults.
Ok, so GUI2exe just won't work on my computer (keeps crashing). So I tried
to run PyInstaller directly. I followed the instructions, and it actually
does make the executable as I ask, but that executable simply segfaults.
It's the same result whether I choose to make a single file executable or a
whole directory for distribution.
I have seen your error report message about GUI2Exe, I'll try to work
on it when I get back from Kazakhstan next week. I am not sure why
PyInstaller gives you a segmentation fault, but you may want to use
the SVN version of PyInstaller as version 1.3 is very out of date.
Ok, so GUI2exe just won't work on my computer (keeps crashing). So I tried
to run PyInstaller directly. I followed the instructions, and it actually
does make the executable as I ask, but that executable simply segfaults.
It's the same result whether I choose to make a single file executable or a
whole directory for distribution.
I have seen your error report message about GUI2Exe, I'll try to work
on it when I get back from Kazakhstan next week. I am not sure why
PyInstaller gives you a segmentation fault, but you may want to use
the SVN version of PyInstaller as version 1.3 is very out of date.
And/or post your troubles on the pyinstaller Google group (or gmane newsgroup).
And/or post your troubles on the pyinstaller Google group (or gmane newsgroup).
I haven't decided if this is worth the effort. I'm a bit frustrated with all the Python packagers. None of them seem to actually work. In turn, I've been playing with the C++ version of wxWidgets and that hasn't been too bad. Developing on C++ is slower than on Python, but at least I can make a static binary and it actually works. The static binary is 2.7MB and I haven't yet made any effort to make it small.
In principle, I'd much rather develop in Python than C++, but if C++ works and Python doesn't...
I guess that one option is to use Python as a RAD tool. Develop the app in Python first and then re-implement it in C++. It seems sad to have to do that because pyinstaller and friends don't work, but on the other hand, I don't have the energy to fight with a packaging tool right now.
And/or post your troubles on the pyinstaller Google group (or gmane
newsgroup).
I haven't decided if this is worth the effort. I'm a bit frustrated
with all the Python packagers. None of them seem to actually work. In
turn, I've been playing with the C++ version of wxWidgets and that
hasn't been too bad. Developing on C++ is slower than on Python, but
at least I can make a static binary and it actually works. The static
binary is 2.7MB and I haven't yet made any effort to make it small.
In principle, I'd much rather develop in Python than C++, but if C++
works and Python doesn't...
I guess that one option is to use Python as a RAD tool. Develop the
app in Python first and then re-implement it in C++. It seems sad to
have to do that because pyinstaller and friends don't work, but on the
other hand, I don't have the energy to fight with a packaging tool
right now.
Daniel, my point of view on this is:
Whenever you run some software and you run into problems I think it is the least one can do is to report the problem to the respective author or mailing list.
Just imaging that you put your software out there and someone tries it and for some odd reason he runs into a problem. Wouldn't you want to know about it?
I think this is even more true with OSS - this is a very cheap way of "paying" the authors something back - if not the authors then the community.
I haven't decided if this is worth the effort. I'm a bit frustrated with all
the Python packagers. None of them seem to actually work.
In principle, I'd much rather develop in Python than C++, but if C++ works
and Python doesn't...
In addition to what Werner said, it's good to remember that if
something doesn't seem to work for you but others aren't complaining
about it, then it's likely that something isn't right with the install
on your machine.
Try to have all the information in one post - I'm sure you've
mentioned which version of Linux you're using (Ubuntu, wasn't it?),
but it's a hassle to search through old messages.
There have been quite a few recent threads here about issues with
default Python/wxPython installs and mixups on downloaded updates on
Linux. It sounds to me that something like that is biting you, but
I'm no expert...
Hang in there.
Cheers,
Scott.
路路路
On Mon, Jan 18, 2010 at 3:18 PM, Daniel Carrera <dcarrera@gmail.com> wrote:
Whenever you run some software and you run into problems I think it is the least one can do is to report the problem to the respective author or mailing list.
Just imaging that you put your software out there and someone tries it and for some odd reason he runs into a problem. Wouldn't you want to know about it?
Fair enough. I'll write to the pyinstaller guys. Tomorrow though. I'm about to go to bed and I'm too tired to think straight.
I think this is even more true with OSS - this is a very cheap way of "paying" the authors something back - if not the authors then the community.
I never thought of it like that. Reporting a bug feels more like complaining than paying
Did you do a bit of googling ?
In truth, I did not. Usually I do, but this time I didn't.