The last time a django core dev looked at DBIx::Class in front of me the response was "shit, we need to steal that".
Sadly I didn't get to catch up with them properly at OSCON to find out if they'd manage to steal much of the awesome stuff yet.
SQLAlchemy probably already has similar features though, so maybe they don't need to.
Ruby can't handle MI. Ruby's metaprogramming seems limited. But I'm not informed. I've had several perl ->ruby guys come back to perl going "hey! it's like ruby but with a flexible object system" to me. But I don't know enough about it to have an opinion myself.
I think you'd have a hard time coming up with something that Ruby's metaprogramming can't handle where Perl's answer would be better than "eval". I could be wrong; I'm equally shady in Perl (I haven't written in it since 1996).
Ruby doesn't do multiple inheritance, though you really do get 90% of what reasonable people do with MI with mixins, which work beautifully.
Sadly I didn't get to catch up with them properly at OSCON to find out if they'd manage to steal much of the awesome stuff yet.
SQLAlchemy probably already has similar features though, so maybe they don't need to.
Ruby can't handle MI. Ruby's metaprogramming seems limited. But I'm not informed. I've had several perl ->ruby guys come back to perl going "hey! it's like ruby but with a flexible object system" to me. But I don't know enough about it to have an opinion myself.