Make Python Script Accessible to Mac/iOS App

I am a developer of an app for Mac and iOS which allows users to save videos from a variety of websites. While my current app handles videos hosted by Youtube and Vimeo, I've discovered *youtube-dl* ([login to view URL]), a Python script that supports many more hosting sites. It would be an amazing addition to my app to take advantage of youtube-dl's broad support. In order to do it, you have to embed a Python interpreter into an Xcode project, supporting both iOS and Mac. It's further complicated by the fact that the code which needs to run this must be in a framework — every example of a working Python interpreter inside an iOS app suggests that it must take over the whole project, patching main.m and injecting the interpreter at startup. This has proven to be beyond my capabilities, so I'd like to outsource it to someone with better skills than I in this regard. I have put together a template project that you can work with -- [login to view URL] Here, you'll find an app structured similarly to my actual app. It has a main iOS and Mac application target, and an iOS and Mac framework. The main file in the framework is "youtube.m" (inside the iOS framework, which can share files with the Mac framework), where'll you'll see my proposed insertion point for your work. I need: * a working Python interpreter integrated into this project. I was able to use Python iOS Support ([login to view URL]), and working with the developer of that project, built a version of Python that runs on 3.4 with all architectures included, and I can share all that knowledge with you if required. In my own trials I was able to at least get this far (though it's not included in the Github template above) * a wrapper script in Objective-C (actually WTH, Swift if fine too if you're bent on it!) that interfaces with the youtube-dl executable and returns the output of its simulation options only (notably, a dependency of youtube-dl is ffmpeg, which isn't necessary to run this version, because I just want the JSON, not the actual video file. So the "-j" option is all the support required). Whatever process/mechanism that you use to put this together, I'd like it to be explained to me and repeatable, such that I could: * Update this to run with a future version of Python; * Update this to run with a future version of youtube-dl; and * Post the solution online, open sourcing it so that future me's don't get bogged down in this kind of BS. :-) In my trial phases with this work, I've come across other potential mechanisms for performing this. For example, I've explored using Cython and Nuitka as a way of converting the Python to C, and then hooking it up in my project. I'm open to that approach, but the same rules apply as above: it needs to be repeatable and shareable.