I fixed it by calling pyglet.image.load on the file before passing it on to the cocos sprite.
Before it was just cocos.sprite.Sprite directly. (it worked before I started rewriting the code) It worked without calling pyglet.image.load if the path is not absolute, but links to a subfolder of path.dirname(__file__) directly. I think this is a bug in pyglet: Unless I'm missing some important subtle functionality gained from this behaviour. -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/groups/opt_out.
