Ok. Is it correct to say that pyglet can still be used on OSX 10.6 64- bit by some hoop-jumping? You must use a 32-bit compiled Python for it? I'm not on 10.6 or 64-bit myself though that could happen some day - what must one do to use pyglet as-is on Snow Leopard 64? Of course, someone able to do the work would be better :)
Also, an addendum to my first message on this thread, I found this discussion of possible 1.2 features: http://code.google.com/p/pyglet/wiki/ReleaseSchedule -b On Jan 24, 10:49 am, Tristam MacDonald <[email protected]> wrote: > On Sun, Jan 24, 2010 at 1:35 PM, Ben Smith > <[email protected]>wrote: > > > I'm afraid I haven't kept up with the developments on the OSX things. > > I am currently without a Mac (64-bit or otherwise), so my Cocoa backend is > unfortunately on hold until such time as I manage to acquire one - not > something I can afford in the near future. If anyone feels up to taking a > stab at completing the port, I would be glad to offer help and advice. > > Also, to open up a fun can of worms - now seems like a good time to > > > move to a dvcs, particularly Mercurial since google code supports it. > > +1 for Mercurial. While git has some advantages, the ease of transition from > SVN to Mercurial seems a win to me, along with the ability to stick with > googlecode. > > -- > Tristam MacDonaldhttp://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.
