Thanks for the report! Indeed there was a bug which was solved a couple of days ago in pyglet. At the moment you have 2 options:
- Wait for pyglet to release version 1.3.2
- Pull from bitbucket repo the pyglet-1.3-maintenance branch where the bug fix landed
Sorry for the inconvenience.