We’ve started direct planning towards 0.3 as discussed in our forum at http://www.volumesoffun.com/phpBB3/viewtopic.php?f=14&t=520. I imagine that we’re a few months out but since I’m in the middle of writing my PhD thesis at the moment, time is a little short. In the mean-time, you could check out the develop branch in Git to see all the things mentioned in this blog post.

I’m currently writing a blog post giving more details of the Python bindings (and soon after another post about trying to do callbacks). I’ve found that using SWIG’s ability to insert native code for certain situations to be very helpful though my knowledge of the Python C API is limited.

If you have any specific questions or things you want to talk about, please do pop into our forums.

I am eventually putting this in T3D and hence C++, but I wanted to play around with the fast prototyping capability of Python. Also, I have added Python to T3D using SWIG, but all the interfaces I did by hand. I found SWIG really great for helping me handle data structures, but many things I had to build as native Python API interfaces such as my callback system. So I think it is great that SWIG can generate stuff for you, however it really pays to know how to create the Python C functions from scratch. I was able to completely control the interface that way. T3D is an engine so my experience may not really translate to a library though.