Yesterday I finished of what is hopefully the last testing release of the product I'm responsible for, assuming no major problems it will go gold soon. This means I can start on doing some new development work. The thing I'm working on next will be done in a scripting language as basically the task of ensuring configurations are correct and properly setup is a) not performance critical and b) a hell of a lot easier than wrangling strings in C.
While most of the scripting stuff on the product is written in perl I've been contemplating doing something a bit more major with Python. While the perl I write (example) probably looks more like C with extra punction marks compared to the code of a seasoned perl wrangler I still occasionaly get tripped up by it. In contrast my experience with Python so far has been much more pleasent, no doubt helped by the ability to experiment in an interactive python shell. So far it's behaviour has been unsurprising. We shall see how I feel about it after this piece of work :-)
Of course the first thing to do before starting out on this course is to see if my editor is configured and ready. I've immediately walked into the python.el and python-mode.el schism. I'm going with python-mode.el for the time being but at the moment I'm not doing much more than run iPython as a inferior shell within Emacs.