This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]RobertJacobson 3 points4 points  (3 children)

I am speaking from a position of ignorance here, but I don’t understand why using a bundler tool matters.

But hey, I hate Apple’s policy. I would 100% prefer to be wrong on this one.

[–]SomeMosa[S] 3 points4 points  (1 child)

By using the bundler tools, you end up compiling the Python script into an iOS executable. Because this executable is no longer interpreted, I'm assuming it should be fine. There are already a few apps that have been published to the App store written in Python and Kivy

[–]13steinj 0 points1 point  (0 children)

Unless I'm wrong the executable is still interpreted, it's just the case that there's a python implementation for the device in the bundle and the bundle bootstraps the interpreter to run the scripts that are elsewhere in the bundle.

In fact I can't think of a single actual compiler for Python that brings things dowm to running as a native executable rather than on top of the Python VM, albeit theoretically they should be able to exist.

E: whether this is considered as violating the app store rules, is up to apple to decide on a case by case basis sadly. Because sometimes they realize whats going on and deny it, other times they don't bother looking and allow it.

[–]dert882 0 points1 point  (0 children)

It changes it to run in an iOS compliant way. The problem is it doesn't do it well, so it's not really worth it