On Fri, Nov 25, 2011 at 2:19 PM, Phillip Nguyen <[email protected]>wrote:
> I feel like it would be a good idea to have an official release of 1.2 > containing the PyObjC backend before I start completely changing > what's in the trunk. Not a bad idea, and I am happy to help with testing/fixing trunk for that purpose. > > 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. > A solution that doesn't support PyPy is a non-starter for me. Since PyObjC is unlikely to ever be well supported under PyPy, that implies we either: a) port PyObjC to ctypes, and continue to depend on PyObjC, or b) port pyglet to ctypes. The former being cooler (and having wider application than just pyglet), while the latter is considerably less work. *** Philip: I'm going to have some free time coming up, and I want to get the ctypes implementation up and running (particularly on pypy). I'm not that familiar with distributed development using mercurial - does it make more sense for you to grant me write access on the ctypes repository, or for me to clone it and us to push-pull back and forth? -- 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.
