So if I learn Python, what could I do with it?
I know I should research this myself but you said you have experience with it so..
Well, you can do the same things as with any other languages. In that aspect, it doesn't really matter what language you choose. You will most likely start of with using it as a calculator, then you'll probably dive into a couple of simple for- and while- loops. Eventually you'll probably do some string manipulations. The basic stuff is the same in all languages. The syntax isn't though. And that's why Python is often recommended for newbies, because its syntax is easy to understand. Another pro is the availability of documentation. If you are wondering how to solve a certain problem, the answer is often only a short Google-search away. There is most likely someone who has encountered the same problem as you with big languages such as Python and C. If you decide to start with TorqueScript or another small language, you have to do much of the problem solving yourself.
Personally, I use Python (and MATLAB) for scientific purposes. Modelling dynamic chemical systems, for example. Those models often involve numerical solving of quite complex differential equations, which are very time consuming (or even impossible) to solve by hand.
But unless you are pursuing a career in mathematics or engineering, you probably won't need to learn that kind of programming :P
Here's a list of applications:
http://www.python.org/about/apps/ ,
http://python.about.com/od/gettingstarted/ss/whatispython_all.htm ,
http://en.wikipedia.org/wiki/Python_(programming_language)#UseAccording to wiki, Civilization 4 and Battlefield 2 use Python. So that's cool.
"An important goal of the Python developers is making Python fun to use. This is reflected in the origin of the name, and in an occasionally playful approach to tutorials and reference materials."
"The Zen of Python
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!"
