Why not Python?

The iOS stack is growing as developers find ways to use their favorite languages to power their apps. Why not Python dives into one of the options: Python. We’ll explore about how to get Python running in your app, call Python code from Obj-C or Swift, and how to structure your project, as well as the practical tradeoffs of running Python in a real-world app.

Transcript

1. Why not Python? @DanaRSilver
2. The iOS Stack • Swift, Objective-C • C, C++ • JavaScript • C# • Go • . . .
3. Python and iOS • History of support on macOS • Python is designed to be embedded • Existing packages bridge the gap • Practical use-cases • A chance to explore the underside of Python and solve a few good puzzles
4. So you want to embed Python CPython Python.patch - unsupported_sys_call + #if TARGET_OS_IPHONE $ clang -arch armv7s CC & LD Flags
5. Call me Python! #import <Python/Python.h> /* Start the interpreter */ const char *code = "print('I am Python!')"; PyRun_SimpleString(code);
6. Patterns and “Best Practices” • Keep all your Python together • Use pip and requirements.txt ./python ├── app │ └── __init__.py └── packages └── requirements.txt
7. Tying it all together
8. Practical Considerations • Embedded Python takes maintenance • Abstracting the Python C API to scale • App size
9. Why not Python? @DanaRSilver