rubypython

> To explain what I mean: you can't import a Ruby library into a Python program. Not to detract from your overall point, but there's actually a lot of Ruby <-> Python interop stuff out there. At one point I was playing around with importing C++ modules exported via boost::python to consume from Ruby (admittedly only for a toy project.) I'm not sure if I was using RubyPython[1] - searching google turns up multiple options. And I'm not sure how well any of them hold up in production. And then on the CLR there's both IronPython and IronRuby, which might play well together. [1] https://github.com/halostatue/rubypython (EDIT: A 4 emdashes long run on sentence? I can do better...)

This claim is incorrect: Aman Gupta did not create RubyPython, nor does he claim to (and Aman's repo linked above even shows that his repo is a fork of my repo). Aman has provided some comments, discussion, and code back to RubyPython over the last few days. I know this because I've been chatting with him and pulling his modifications back into the main GitHub repo[1] (which happens to be mine) and pushing them back into the canonical repo on Bitbucket[2] (which is the original creator's repo). RubyPython was created in 2008 by Zach Raines, rewritten to use FFI in late 2010. Steeve Morin forked it as Rupy (apparently with Zach's blessing as Zach pointed me to it when I posted a bug fix to Zach's code) earlier this year. I got involved shortly after Steeve's fork. After some discussion, we (Steeve, Zach, and I) unforked Rupy back into Ruby