On Mon, Mar 7, 2011 at 8:28 AM, Charles Brandt <[email protected]>wrote:
> On 2/28/11 7:45 PM, Richard Jones wrote: > >> Python 3 doesn't include the MacOS module which is used by non-cocoa >> pyglet. Unfortunately the cocoa branch doesn't do Python 3 code >> translation :-) >> >> > Is this a good time to merge the cocoa branch back to the 1.2dev trunk? A question for the Cocoa branch developers: Does the Cocoa branch treat Cocoa as a fourth "platform choice" for pyglet, in addition to linux, windows, and (macos) carbon? If it does, and if running pyglet on a Mac would choose carbon by default (except in case when carbon can't possibly work), then although I know essentially nothing about the Cocoa branch, I see no reason it couldn't be merged at any time. If it is, instead, an alternative implementation of the existing "mac" platform choice, then I don't see how it can ever be merged without changing that, until it becomes so complete that no one ever needs carbon again. - Bruce Smith -- 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.
