Aaron Seigo, a noted developer for the KDE project, recently blogged about a case for python. The gist is that he feels that python is a suitable language for people to just get into (think VBScript).
Which came back to Aaron and his response that he in fact hearts Ruby too, though he thinks it doesn’t have the same selling power as python to the VB crowd.
Aaron’s point (at least as I understand it) is that he thinks that the open source desktop communities should try and center around one main scripting language to support, and he think that python has the gravitas to be that language. He even states the case that he prefers Ruby and would personally like to use it instead.
While I think Aaron’s python stoicism is well intentioned, it doesn’t seem necessary. If the history of the open source desktop shows us anything, it’s that that having multiple choices seems to be way preferred way of business. Look at the Ubuntu project, which targeted creating a Linux distribution that set everything up for the end user in one certain way. Oh, there were choices, but the default system was predefined so as to make it quote-unquote-easier for the end user.
For Ubuntu, the preferred desktop was Gnome. It wasn’t long after that Kubuntu was released - a KDE based Ubuntu distribution.
The point is that if the desktop communities unite around python, it won’t take long for a group of rubyists to create a project that does the same thing. Similarly, if the desktop communities unite around ruby, a python project will most likely get started.
The KDE and Gnome projects are already used to this. They have a combined goal, but competing methodologies.
In the language issue, you should just choose whatever works best for you. After all, you’ve already done the same for your desktop.