Re: Cocoa Python broken in Leopard??
Re: Cocoa Python broken in Leopard??
- Subject: Re: Cocoa Python broken in Leopard??
- From: Bill Bumgarner <email@hidden>
- Date: Wed, 7 Nov 2007 00:57:31 -0800
On Nov 7, 2007, at 12:46 AM, Uliano Guerrini wrote:
the problem arises when you want to use Quartz "somewhere" to do
something useful and this "somewhere" is likely to be some subclass
of NSView (or some file imported in that subclass), well, if I'm not
wrong, that subclass in order to work should be imported in the
main.py file before
AppHelper.runEventLoop()
which is the call that fires up the window server
If you import it there, you get the errors as indicated by the OP for
exactly the reason I described -- the Quartz module must be imported
*after* the AppKit has brought up the Cocoa stack, including the
window server connection, because the act of importing the Quartz
module tickles the window server connection (among other things).
Whether or not this is a bug in the Quartz module is semi-debatable.
It is certainly inconvenient, but it is not unheard of for Python
modules to behave this way.
anyway, py2app without aliasing works, in pyobjc-dev they say that
they'll find to fix what to them seems a problem to be fixed
Actually, if you read the pyobjc-dev thread, it states quite
explicitly that importing Quartz before AppHelper.runEventLoop()
causes the problem *and* that this isn't necessarily a bug.
b.bum
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden