All activity
HeeJun Gwonleft a comment
We built PylibKit out of frustration. Every time we wanted Python in an iOS/macOS app, more time went into packaging CPython, native extensions, SSL/libffi, codesigning, simulator/device splits, and CI reproducibility than into the actual product. So we changed the model. Instead of “embedding Python,” we treat Python as a versioned SDK dependency. PylibKit: 1. Bundles CPython and curated,...
PylibKit: Python as a Swift SDKCPython + curated wheels, wrapped in Swift async APIs
PylibKit lets iOS/macOS apps use Python libraries—including C-extension and Rust-backed wheels—without exposing Python to app code.
Everything is bundled into a single Swift XCFramework.
You call generated Swift services with async/await, receive Swift types, and never touch PythonObject.
We handle CPython, pinned wheels, asyncio safety, threading, signing, and reproducible builds—so app teams can focus on features, not toolchains.
PylibKit: Python as a Swift SDKCPython + curated wheels, wrapped in Swift async APIs