"A lot of elitist dinosaurs evident in these comments"
get off my lawn, you young whippersnapper! [heh]
Seriously, don't use an interpretive programming language for ANYTHING that requires performance, especially one that has built-in garbage collection and "duck typing", regardless of whether it does 'just in time compiling to pseudo-code' or not.
And more often than not, "object oriented" is _HIGHLY_ overrated [especially when it comes to system performance]. This goes TRIPLE for VMs and shared hosting... "oh but it doesn't matter because CPUs are so fast these days, and memory so cheap" until you try and run a bunch o' stuff simultaneously in multiple VMs or shared hosts, and then you find out what kind of impact inefficient code has. Yeah.
I wouldn't write a massive system in Python. I'm having to FIX one, at the moment (uses Django) and it's seriously in need of a MASSIVE re-write. Fortunately, I quickly figured out how to invoke an external program [written in C], and that solved MOST of the performance issues.
Yeah, I _do_ keep saying that about Python invoking a C program. It _is_ 30 times faster this way, with that one specific example. And it makes a very valid point that I want to express to as many people as possible: Do NOT attempt to force Python into a 'C' shaped hole. You'll go bat-guano insane trying. Use a language that's more suited to the task, and Python as the glue if you want to [for which it works very, very well, in my opinion].
but writing a massive system in Python? I'm old enough to remember how *CRAPPY* RSTS/E was, and it was written in COMPILED BASIC. So, "NO" to 'massive system in Python'. That is, if you want PERFORMANCE out of it.
'children' icon because, youngins these days...