On Tuesday, June 12, 2012 11:16:03 PM UTC+1, swiftcoder wrote: > > On Tue, Jun 12, 2012 at 5:12 PM, Rui Carmo <[email protected]> wrote: > >> I may have missed something here. What's wrong with the stock Python in >> Lion? >> >> (I'm asking because that's my default work environment, and I've had good >> success with it). > > > Not everybody likes the stock python. It is however the simplest to get > pyglet running at this point (and the environment that pyglet is probably > the most tested with) . > > On Saturday, June 9, 2012 6:16:51 PM UTC+1, Jonathan Hartley wrote: >> I'm running on OSX, on which I understand Pyglet needs a 32 bit Python >> executable. >> > > That hasn't been true for a very long time. > > The issue was that Carbon is not supported under 64-bit, but we added > Cocoa support a long time back. You don't even need the ctypes branch to > take advantage of that - there is an older PyObjC port to Cocoa in the main > repository. > > -- > Tristam MacDonald > http://swiftcoder.wordpress.com/ >
Many thanks for the explanation, I had misread the "pyglet requires PyObjC when in 64-bit Python" exception to mean that things would be simpler if I was using a 32-bit Python. "pip install pyobjc==2.2" works just fine, pyglet runs happily, and all the "lipo" and "arch" wrinkles can be deleted from my scripts/README. Much rejoicing. Jonathan -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/Tuco4OpFTvQJ. 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.
