On Sep 28, 2012, at 01:35 PM, "Diez B. Roggisch" <deets@...> wrote:
On Sep 28, 2012, at 1:24 PM, Ronald Oussoren wrote:
> On Sep 28, 2012, at 11:14 AM, "Diez B. Roggisch" <deets@...> wrote:
>> Bump. Nobody seen this? I tried with a freshly re-installed Python 2.7, with new pyobjc and py2app 0.6.4. Same issue. It seems kind of random at which packet it crashes, if that help.
>> I'm really looking for a solution, because I finally would have an actually commercial project I *need* to ship an app, instead of private stuff I can run as aliased bundle, so any help is much appreciated.
> I haven't seen this before. You could try running with pdb to see if that gives you more information?
I tried, but it failed randomly, so pdb wasn't of much use.
The fun thing is: I wanted to investigate further, and re-iterated the py2app some times. And lo and behold, eventually it would work.
So I started working on my project for now, as it seems I can get things to work eventually.
> Can you build the sample projects that ship with py2app and pyobjc? If those work you could try to minimize your setup.py file and then add in stuff until building fails.
I did that - and funnily enough, it works. For all the examples in
So it might be something that is local to my project. Which is strange, but heck, nothing is impossible. I will try & see if the issue rises again. The new project I started will feature a lot of the code & modules of the failing one (which was the reason I picked it in the first place), and I'll keep an eye on if and when this will happen again.
Thanks for taking time to think about this!
A sample project that demonstrates the problem would be very helpful, I'd love to get rid of vague crashes like this. Building such a project could require a lot of work though.