On Thu, Nov 24, 2011 at 7:26 PM, Tristam MacDonald <[email protected]> wrote: > 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 That's a great conversation to have. To help determine the best long-term strategy for 64-bit support on OS X, I would add the questions: - What are the pros/cons of a ctypes implementation in general? - What are the pros/cons of a PyObjC implementation in general? >From the (admittedly limited) information I have run across so far, it would seem that ctypes implementation has the major advantage of being able to be run by more python environments than the PyObjC implementation, and the disadvantage of being more work to implement. If that major advantage is important to people willing to contribute coding time. I've been a lurker on the PyObjC mailing list for many years now, ever since I heard of it, got interested in maybe using it, but then never did. From what I see, PyObjC is a one-man project that doesn't get a whole lot of attention, as the mailing list is extremely low traffic. Occasionally when things break, or changes happen to OS X, PyObjC seems to take awhile to catch up. To the his credit, that one guy seems to do a great job when he has the time to work on it. I don't know much more about it than that. I've never used ctypes. All I know is the basic information that it's a built-in way for Python to wrap libraries in pure python. ~ Nathan -- 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.
