Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You can't. The new SDK agreement <a href="http://daringfireball.net/2010/04/why_apple_changed_section_331" rel="nofollow noreferrer">prohibits using original languages other than C, C++, or Objective-C</a>, and the SDK agreement has always prohibited dynamically interpreting code. There's some ambiguity about how these rules will be enforced, but to be safe, it's best to avoid other languages until the kinks get worked out. </p> <p><strong>EDIT:</strong> In addition, as far as I know, there's no current technical way to run Python on the iPhone, as per <a href="https://stackoverflow.com/questions/43315/can-i-write-native-iphone-apps-using-python">this question</a>. I've heard of embedding Lua in iPhone apps, but not Python. You can do <a href="http://www.saurik.com/id/5" rel="nofollow noreferrer">Python with a jailbroken iPhone</a>, but not through the app store. </p> <p>The Ruby situation is almost as bad, as per <a href="https://stackoverflow.com/questions/219653/ruby-on-iphone">this question</a>. The iPhone doesn't ship with a Ruby interpreter, and <a href="http://www.mail-archive.com/macruby-devel@lists.macosforge.org/msg03368.html" rel="nofollow noreferrer">compilers</a> are a long ways off from working. Rhomobile works by packaging an interpreter and framework with the executable, which I highly doubt will make it past the new SDK agreement. If you really want to use Ruby, Rhomobile would probably be the best bet (as implementing your own interpreter would probably be a lot of work, and equally as unlikely to be approved). It's a rather depressing landscape at the moment--the most we can hope for is that MacRuby will eventually work, and Apple will approve it. That's a long ways off, though. </p> <p><strong>EDIT 2:</strong> I also just found out about <a href="http://www.tinypy.org/" rel="nofollow noreferrer">tinypy</a>, which could potentially work for Python. I doubt it would run real libraries though. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload