After 2 years building an algorithmically intensive desktop app in Python that ships on 3 platforms, my strongest recommendation is to avoid all of these fancy environments that change the way Python is used or internally works, including Stackless, Twisted, SWIG, Psyco, Pyrex, and so on. In my experience they tend to 1) introducing subtle bugs and 2) make traditional debugging more difficult.<p>Generally very little of the code needs the burden of any complication beyond "real" Python. Where you specifically need more performance tuning, and you are sure that a different data structure or caching doesn't solve it, and it's not one of the many situations someone else has already made a C module for, I suggest using "real" C, in the standard, well documented, debugged and maintained approach: write a Python module in C using the Python/C API.
There is no silver bullet. It's a nice looking list but pretty useless, it says that you made an original mistake choosing Python, now grab a different technology and rewrite it.