hi,
thanks for that excellent trick.
it sounds like this is a problem of py2app and its PyQt recipe. this conflict
is very dangerous since it could lead to frustrated users of your apps and
might give developers a hard time.
could that be included to py2app? also deleting the Qt.debug files fr
Brilliant...it turned out that the Qt libraries were being loaded *twice* –
once from inside the bundle and once from the libraries on my computer.
The hack fix was to create a qt.conf file inside Contents/Resources and give
it a bad path...this way only the libraries inside the bundle are being
l
Maybe your app is loading the wrong libs?
Try running from the terminal and printing the libs that are being
loaded:
$ cd /path/to/your/bundle.app/Contents/MacOS
$ DYLD_PRINT_LIBRARIES=1 ./your_app
Check if all the Qt and PyQt libraries loaded are in your bundle.
-- Emanuele.
On Dec 15, 200
It's a memory issue with Qt I think. The other interesting thing is, this
problem doesn't occur if I build the app in alias mode with the -A
flag...but of course that's not too useful if I want to distribute
applications.
Here's the issue I get:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KE
On Dec 15, 2009, at 12:17 AM, aditya bhargava wrote:
> I'm getting some strange results running py2app on my machine. It works fine
> with most scripts, but any time I use it with a script that uses PyQt, the
> built application immediately quits and gives me an "unexpectedly quit"
> message. I
Hi python users,
I'm getting some strange results running py2app on my machine. It works fine
with most scripts, but any time I use it with a script that uses PyQt, the
built application immediately quits and gives me an "unexpectedly quit"
message. It's not the code, because I tried py2app with a
