unholy

Not just on the surface. See the ruby to python bytecode compiler: https://github.com/whymirror/unholy

It's not a version of Ruby. And Ruby and Python are roughly equivalent, so if you can convert one, you can likely convert the other. (see also https://github.com/whymirror/unholy)

> Python and Ruby are really similar. Yes they are, as seen in the _why's old project: https://github.com/whymirror/unholy > Compile Ruby to Python bytecode. And, in addition, translate that bytecode back to Python source code using Decompyle (included.)

> Didn't we learn from C++ that multiple inheritance is good in theory but in practice a horrible idea? No, we learned from C++ that C++ multiple inheritance is an atrocity. Python's MI works in a clear and obvious way, similar[0] to how the Ruby inheritance chain is clear and obvious. MI really doesn't fit Ruby though, and IMHO would look too bolted on. Most of the time the problem is people beating the platform they develop on into submission, instead of embracing it by getting a clear picture of what happens. [0] As _why said[1], python and ruby are damn close: you can easily get something similar to Ruby's modules and inject them dynamically in the inheritance chain: https://gist.github.com/3951273 [1] https://github.com/whymirror/unholy

This is like the bizarro version of the late _why's unHoly ( http://github.com/whymirror/unholy ), the README for which contained this: "You know, it's crazy that Python and Ruby fans find themselves battling so much. While syntax is different, this exercise proves how close they are to each other!" ...Which is the apparent reason for naming the codebase "unHoly". A code ambassador to try to mediate a peaceful resolution to the holy wars. (Pyhad? Rusades? I bet _why could have come up with a better name.)