That will probably get removed soon. I believe Apple already made him get rid of a similar feature in an update for Pythonista (I could be remembering wrong though… maybe they made him remove something else?).<p>EDIT: Oh, wait, found it:<p><a href="http:&#x2F;&#x2F;mjtsai.com&#x2F;blog&#x2F;2014&#x2F;06&#x2F;12&#x2F;pythonista-in-app-store-peril&#x2F;" rel="nofollow">http:&#x2F;&#x2F;mjtsai.com&#x2F;blog&#x2F;2014&#x2F;06&#x2F;12&#x2F;pythonista-in-app-store-pe...</a><p>“<i>So what was the problem Apple had with the previous version? Turns out, they didn’t like the Open in… menu integration I had added in 1.4 because that would allow you to import executable code from external sources. My theory is that this policy is in place to prevent apps that circumvent the App Store, e.g. by offering downloadable games that don’t go through Apple’s review (and revenue chain via in-app purchases).<p>[…]<p>I’m sad to see this feature go. It wasn’t just a convenient way to import scripts, it also enabled some pretty interesting automation workflows that could process the contents of pretty much any kind of file you could access on your iOS device.</i>”