On Thu, Nov 24, 2011 at 1:28 PM, Phillip Nguyen <[email protected]>wrote:
> On Nov 24, 10:11 am, Nathan <[email protected]> wrote: > > So, Philip, are you _maintaining_ a separate ctypes-based pyglet fork, > > then? I've been focusing on AVbin a lot lately, but I really need to > > get my project(s) running pyglet on OS X again. Where should I focus > > my efforts, trunk or evilphillip-cocoa-ctypes? > > No, I'm definitely not maintaining anything at this point. > You should focus your efforts (thank-you, btw) on the trunk. > > --phillip Let be very explicit here. As I understand it: pyglet trunk contains a Cocoa implementation via PyObjC, which works on Apple's stock python, and occasionally works on other python packages, but notably does not work on PyPy. evilphillip-cocoa-ctypes, regardless of whether it is maintained, contains a Cocoa implementation via a custom ctypes layer, *without* PyObjC, which should (when complete) run on *all* python packages, including PyPy. Am I correct? -- Tristam MacDonald System Administrator, Suffolk University Math & CS Department 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.
