Skip to content

TypedPython 3: ship compiled modules through the pypackpack native/mixed slot #25

Open

Description

@b-re-w

What

Hand the Cython output of M2 to pypackpack's Cython backend slot (native/mixed build level) so the compiled extension lands in the app bundle. Desktop is required. Android arm64 is included if pypackpack's NDK backend is in place. iOS is excluded unless the Xcode backend is, because those backends are placeholders today.

Dependency

pypackpack: who defines the slot's interface is still open (raised to the maintainer). This repository only supplies the sources and build flags.

Done when

The sample app, built from the bundle on desktop, imports the compiled module, the in-app speedup is measured, and the GIL and free-threaded flavours are not mixed up (pypackpack path key, still undecided).

Activity

  1. added a commit that references this issue on Nov 5, 2026
  2. b-re-w commented on Nov 5, 2026

    @b-re-w
    MemberAuthor

    Step 1 landed in develop via #372: python -m typedpython emit-c and the manifest (format version 1, docs/design/typedpython.md 4.3.2a). Step 2 (Gradle task mapping the manifest to BundleRequest.nativeModules / notNativeModules) is next for the Gradle-plugin owner. pypackpack develop c81ed5f: ExtensionCompiler.kt has the data types and ExtensionCompilerInterface only, no implementation.

  3. added 2 commits that reference this issue on Nov 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions