As a counter example, I once had a hard time getting pygame running on OS X. I don't remember exactly what the issue was, it may have had something to do with multiple versions of python installed on my machine, but it was enough of a pain that after a couple of hours trying to figure it out I decided I didn't care enough about checking out pygame to work it out. This might have been the kind of thing that someone more experienced in python would have known how to solve immediately, but for me at the time it was too much.
On the other hand, on other machines it was a breeze to set up.
which works, although installing from pygame's HEAD doe snot sound engaging. What's more, note the date and title.
Pyglet's master branch still uses Carbon, so you have to use a years-old experimental Cocoa branch, which won't be merged because it requires pyobjc[1]. This in turn requires pyobjc, which requires a little trickery to install:
export MACOSX_DEPLOYMENT_TARGET=10.6 # else it'll fail at finding some libs, and stubbornly tries to stay in 32-bit land
easy_install pyobjc-core==2.3 # else pyobjc fails to build this by itself
easy_install pyobjc==2.3 # finally
Really? Because I couldn't get the Ubuntu package or the one from pip to work. And the last article on HN that mentioned it has the author having to install it from a bundle on the pygame site, which is also what I ended up doing before moving on.
On the other hand, on other machines it was a breeze to set up.