The issue seems to be your video card/cards. I have pasted part of the pyglet FAQ below -- hopefully your situation falls into one of these? Does this mean that you cannot run pyglet at all? (e.g., try playing something like this one which also uses pyglet).
Sorry that my game is not compatible with your system.
Best wishes, Ben
I get an error "Unable to share contexts" when creating a window
* pyglet needs to share the objects between OpenGL contexts. In pyglet 1.1 and later, even a program with only one window will have more than one context. * The error can occur if you are trying to open windows on different display devices (for example, two different video cards). * If you have only one video card, then you likely have a faulty driver or video chip. The following devices have been known to exhibit this problem: Ancient NVIDIA drivers (older than 30.82), Intel 965 (aka GMA 3000/3100) in some situations, Intel 946GZ, Intel cards with drivers older than 18.104.22.16891 (about end of 2003 year), ATI FireGL with OpenGL version older than 2.0.5284 (~2005), S3 ProSavage/Twister. (This list was copied from https://mollyrocket.com/forums/viewtopic.php?p=2891; only Intel 965 and 964GZ chips have been observed with pyglet exhibiting this behaviour). * If you've determined that your video driver or device is at fault, your best option is to upgrade, as most pyglet applications require more than one context. If you're developing specifically for your (faulty) device, you can set the environment variable PYGLET_SHADOW_WINDOW to 0 and limit yourself to using a single window.
Assuming this is the only problem: In "src/game.py" you can replace "Exception as e:" with "Exception, e:" to make it python2.5 compatible (i hope!)
Let me know how it goes, if it works I'll bundle a Python2.5 src version.
EDIT: Just saw your python3.0 comment ... Yep Python3.0 breaks the old "print foo" syntax. I've been trying to adapt but some things slip through. The py2to3 util should fix all that ... but i doubt pyglet works well with py3.
thanks for the info. You only need to run run_game.py, but using python 2.5 obviously has caused some issues. Sorry about that. As for the distribution stragety -- You only need Python to run the game -- if the one other dependency (AVBin) isn't found then the sound is disabled, but the game still runs.
I have one suggestion if you don't want to upgrade your python version, delete all the .pyc files in all the subdirs, then try running it again. If that doesn't work then I'm out of ideas. :P
You should check out the other pyweek8 entries (there's over 50 i think), as they are all based on the same theme: "Get off my lawn".
I've added some screenshots to the game page, and have embedded them in the original post here also.