List of game components with Python bindings

I think it would be useful to everyone using PyOGRE to create a big list of game engine components that have Python bindings and could be used for creating a complete 3d game engine.

What libs and components do you know of that fill the gaps that OGRE doesn't cover or that adds to OGRE's capabilities (ie, PLSM2) and can be used as an extension of Python? Please list any and all, with a link if possible.

Thanks in advance for any replies!

Here are some things I've found so far:

PyODE for physics
PyOpenAL for audio
PyOgg for .ogg playback (very old though)

1) pysonic for sound. (uses fmod, which isnt free for commercial use)
2)twisted comes to mind for networking.
3)pyro for networking (is like java rmi. so is pretty convenient to use, you can use remote objects. If youre trying a card game, strategy etc, i think this would be great. On the other hand I dont know how good this is for realtime stuff. Also a disclaimer, it uses pickle to serialise objects which is known to have its pitfalls (malicious python code))

1) pysonic for sound. (uses fmod, which isnt free for commercial use)
Sweet! I had never heard of this before (no pun intended).

There's a link to the PySonic project page from the PyOgre wiki main page http://www.ogre3d.org/wiki/index.php/PyOgre. Well worth checking out if you haven't looked, especially for the high-quality PyOgre tutorials and links to other useful Python projects.

Twisted is a great networking library, and I'd strongly recommend it over Pyro.

As sebpotter mentioned, I've started on such a list on the wiki. Please, feel free to add more links to it. It would be neat to have a whole page dedicated to it as well, with more descriptive texts of how the libs might be used together with PyOgre.

Just thought I'd add to the list my project:

OIS - ObjectOriented Input System
http://www.sourceforge.net/projects/wgois

Currently, (AFAIK) it only wraps version 0.3.0 of OIS though. Version 0.4.0 should work ok (it is an addon project, and I do not maintain it). I do not believe I made any breaking interface changes to OIS 0.4, mostly bug fixes and the addition of force feedback.

It is only available from cvs - oisaddons/python/ module.

Currently, (AFAIK) it only wraps version 0.3.0 of OIS though
It works fine with 0.4, although I had to skip wrapping Effect::OIS_INFINITE to get it to compile without an unresolved external.

@Istari

Nice work

I'm not sure what the deal is with the OIS_INFINITE being unresolved It is definately defined in OISEffect.cpp.