On Thu, Sep 3, 2009 at 8:30 PM, Nathan <[email protected]> wrote:
> > On Thu, Sep 3, 2009 at 4:07 PM, Alex Holkner<[email protected]> > wrote: > > > > That's a 64-bit Python binary. pyglet won't work in 64-bits on OS X > > (besides the QuickTime issue here, Carbon also is 32-bit only). While > > waiting for someone with much free time to complete a Cocoa port of > > pyglet, you can download a 32-bit Python from python.org. > > > > Alex. > > Dang. I was rather happy that pyglet worked so well with the system > python before. So if I understand correctly, unless someone does a > whole lot of work to port pyglet<->Carbon interactions to be > pyglet<->Cocoa interactions, I'm stuck with needing to manually > install a 32-bit Python and use pyglet with that. Am I understanding > that correctly? > > ~ Nathan Pretty much. And don't hold your breath on a Cocoa port of pyglet. I took a shot at it earlier this year, and while I have something that mostly works, it isn't anywhere close to a public release, and requires major changes to pyglet itself (because PyObjC does everything arse-backwards). A better solution might be to introduce a C 'shim', which implements the necessary Cocoa code, and pyglet can access directly through ctypes. Unfortunately, this doesn't really fit with pyglet's philosophy (at least IMO). -- Tristam MacDonald http://swiftcoder.wordpress.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
