Of course, this post will pop it right back at the top there, so I'd better add some content.
Currently I'm working with Python. At work, I'm embedding it into the very large existing C++ code base, without using Boost or any other pre-made wrapper. Boost has been a source of problems in the past apparently, so I'm coding this to the C++ API and keeping it quite lean and mean. Sadly nobody on comp.lang.python or the Python/C++ Special Interest Group seem at all interested in answering my questions, so I've spent more time reading docs and searching Google Groups than actually coding. Still, it's working reasonably well, and it's been a good reminder of how C++'s templates and overloading can go some way towards sanitising an otherwise awkward C API.
At home, I'm struggling on with the Turbogears web development framework, which takes various Python packages and loosely throws them together to mildly resemble Ruby On Rails. As with many open source projects and almost all Python projects, documentation is minimal, but it's still far better than it was almost a year ago when I started out with it. Powerful yet under-documented frameworks like this are interesting, because you typically find yourself perpetually replacing your old code as you discover new functionality. This means that the finished product, while you're learning the ropes at least, often takes just as much coding as an ASP/PHP style site, but you finish up with about 1/5 of the code. That's probably good for maintenance, if you can put up with the frustration of incomplete docs long enough to get that far.
