pythonnative 0.50.0__tar.gz → 0.52.0__tar.gz

{pythonnative-0.50.0 → pythonnative-0.52.0}/MANIFEST.in

@@ -1,13 +1,15 @@
 global-exclude *.pyc *.pyo .DS_Store
 include scripts/cibuildwheel.toml scripts/check-distributions.py scripts/release-assets.py
 include .github/workflows/release.yml
+# The renderer core tests the wheels run read these fixtures.
+recursive-include tests/contracts *.json
 recursive-exclude src/pythonnative/native .build/* .gradle/* .cxx/* build/* .swiftpm/* .kotlin/*
 prune src/pythonnative/native/android/build
 prune src/pythonnative/native/android/.gradle
 prune src/pythonnative/native/android/.cxx
 prune src/pythonnative/native/ios/.build
 prune src/pythonnative/native/ios/.swiftpm
-prune src/pythonnative/native/yoga/.build
+prune src/pythonnative/native/core/.build
 prune src/pythonnative/templates/android_template/app/build
 prune src/pythonnative/templates/android_template/.gradle
 prune src/pythonnative/templates/ios_template/build

{pythonnative-0.50.0/src/pythonnative.egg-info → pythonnative-0.52.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythonnative
-Version: 0.50.0
+Version: 0.52.0
 Summary: Cross-platform native UI toolkit for Android and iOS
 Author: Owen Carey
 License: MIT License
@@ -73,18 +73,18 @@ Dynamic: license-file
 
 ## Overview
 
-PythonNative is a cross-platform toolkit for building native Android and iOS apps in Python. It provides a **declarative, React-like component model** with hooks and automatic reconciliation on top of a **native rendering core** written in Swift and Kotlin. Write function components with `use_state`, `use_effect`, and friends, just like React, and let PythonNative handle creating and updating native views.
+PythonNative is a cross-platform toolkit for building native Android and iOS apps in Python. It provides a **declarative, React-like component model** with hooks and automatic reconciliation on top of a **shared C++ renderer core** that iOS, Android, the browser preview, and headless tests all run. Write function components with `use_state`, `use_effect`, and friends, just like React, and let PythonNative handle creating and updating native views.
 
 ## Features
 
 - **Declarative components and hooks:** Describe native UI with Python functions, immutable elements, and typed styles. State, effects, context, and suspense boundaries follow one logical application tree across screens, overlays, and mounted list rows. State updates batch automatically, effect errors reach the nearest error boundary, and event callbacks receive typed records instead of dicts.
 - **React Native's core surface:** `Pressable`, `ScrollView`, `Text`, `TextInput`, `Image`, `Modal`, `FlatList`, and `SectionList` carry the props a React Native developer expects (disabled state and ripples, content insets and snapping, ellipsize modes and pressable spans, controlled selection and key events, sticky headers and inverted lists), plus typed imperative handles on `ref.current` and the full accessibility prop set.
-- **Native widgets and layout:** Swift and Kotlin component managers own UIKit and Android widgets. The shared Yoga C++ engine computes layout beside the controls, using platform measurements for text and intrinsic sizes.
+- **Native widgets and layout:** Swift and Kotlin component managers own UIKit and Android widgets. The renderer core validates commits, lays out with Yoga off the UI thread using platform measurements for text and intrinsic sizes, and skips mounting layout-only wrappers.
 - **Standard asyncio:** Components, effects, event handlers, and tasks run on a dedicated Python application thread. Native UI threads handle widgets, scrolling, and animation frames. Component-owned tasks are canceled on unmount.
 - **Incremental reconciliation:** State changes update affected component subtrees. Versioned bridge commits validate operations and acknowledge revisions; events and controlled text inputs carry identities that prevent stale updates.
 - **Typed, Pythonic authoring:** Components return `pn.Node` and their signatures are their props, so a strict type checker verifies element trees and conditional children. Screens are components whose parameters are their route params (`nav.push(ItemScreen(id=42))`), navigators are module-level values with deep links derived from each screen's `path`, one `Theme` dataclass styles the app and its navigators, `StyleSheet` namespaces give styles typed names, and `pn.Store` holds app state with selector-based re-renders. `pn lint` checks the rules of hooks.
 - **Native lists and navigation:** UIKit collection views and Android recycler views recycle cells for fixed or variable row sizes, grids, sections, and horizontal lists. Native navigation containers present logical screen roots at every nesting level while providers and component state remain in the shared Python tree; navigators take screen options, groups, tab-bar styles, and a navigation ref usable outside components.
-- **Animation and gestures:** Serialized animation graphs support timing with named or bezier easing, springs, React Native's decay model, arithmetic, interpolation, and native scroll and gesture bindings. Swift and Kotlin recognize mobile gestures with Gesture Handler-style activation offsets and update supported animation bindings without Python work on every frame.
+- **Animation and gestures:** Serialized animation graphs support timing with named or bezier easing, springs, React Native's decay model, arithmetic, interpolation, and native scroll and gesture bindings. Gestures activate with Gesture Handler-style offsets and update supported animation bindings without Python work on every frame.
 - **Assets and graphics:** Drop images, fonts, and SVGs under `app/assets/` and reference them by path. Density variants, bundled fonts, a vector `Icon` set, `Svg` drawing, gradients, and blur render natively on both platforms and in the browser preview.
 - **Device APIs:** Python facades expose camera, location, notifications, storage, permissions, keyboard, dimensions and pixel ratio, device info, localization, accessibility settings, and other native services, with a Python fallback for headless tests. Test permissions and platform behavior on your deployment targets.
 - **Native extension SDK:** Python dataclasses and protocols define contracts; `define_component` returns a typed element factory and `pn codegen` generates props and module adapters for Swift and Kotlin. Plugins package native sources and resources, and builds verify matching contracts at startup.
@@ -92,7 +92,7 @@ PythonNative is a cross-platform toolkit for building native Android and iOS app
 - **PythonNative Go:** a prebuilt dev client, published with each release, runs any project without native code, so the project itself is never compiled. `i` / `a` in `pn start` open it on the iOS Simulator (which still needs Xcode installed) or an Android emulator, and a phone with Go installed opens the project by scanning the QR code `pn start` prints. Go isn't in the app stores: Android phones install the APK, and iPhones need Go built and signed with your Apple team. Projects that add native code run in their own debug build, which `pn run` rebuilds only when something native changes.
 - **DevTools and debugging:** `pn start` serves DevTools, with a component tree showing props and hooks (and editable state), a console with a REPL inside the running app, problems with component stacks and source excerpts, network requests, and live performance with trace capture. VS Code attaches `debugpy` breakpoints to Python on the preview, a simulator, or a phone. On device, a dev menu (shake or Cmd+D) offers reload, an element inspector, and a performance monitor, and errors show a screen with the component stack and your source.
 - **Development tools:** Fast Refresh preserves compatible component state, `pn lint` checks the rules of hooks, and `pn init` scaffolds tests, type checking, debugger settings, and CI.
-- **Browser preview:** `pn preview` runs your Python application against a browser renderer with DOM widgets, Yoga WebAssembly layout, and JavaScript animation graphs. It supports iteration on application logic and UI; fonts, platform controls, and device APIs require mobile testing.
+- **Browser preview:** `pn preview` runs your Python application against DOM widgets mounted by the same renderer core, compiled to WebAssembly. It supports iteration on application logic and UI; fonts, platform controls, and device APIs require mobile testing.
 - **App packaging and dependency locks:** `pn run` and `pn build` stage bundled app templates, native libraries, and Python sources. Target-specific wheel locks record dependency versions and hashes for mobile builds. Binary dependencies need compatible mobile wheels; `pn deps` reports target resolution.
 
 ## Quick Start

{pythonnative-0.50.0 → pythonnative-0.52.0}/README.md

@@ -26,18 +26,18 @@
 
 ## Overview
 
-PythonNative is a cross-platform toolkit for building native Android and iOS apps in Python. It provides a **declarative, React-like component model** with hooks and automatic reconciliation on top of a **native rendering core** written in Swift and Kotlin. Write function components with `use_state`, `use_effect`, and friends, just like React, and let PythonNative handle creating and updating native views.
+PythonNative is a cross-platform toolkit for building native Android and iOS apps in Python. It provides a **declarative, React-like component model** with hooks and automatic reconciliation on top of a **shared C++ renderer core** that iOS, Android, the browser preview, and headless tests all run. Write function components with `use_state`, `use_effect`, and friends, just like React, and let PythonNative handle creating and updating native views.
 
 ## Features
 
 - **Declarative components and hooks:** Describe native UI with Python functions, immutable elements, and typed styles. State, effects, context, and suspense boundaries follow one logical application tree across screens, overlays, and mounted list rows. State updates batch automatically, effect errors reach the nearest error boundary, and event callbacks receive typed records instead of dicts.
 - **React Native's core surface:** `Pressable`, `ScrollView`, `Text`, `TextInput`, `Image`, `Modal`, `FlatList`, and `SectionList` carry the props a React Native developer expects (disabled state and ripples, content insets and snapping, ellipsize modes and pressable spans, controlled selection and key events, sticky headers and inverted lists), plus typed imperative handles on `ref.current` and the full accessibility prop set.
-- **Native widgets and layout:** Swift and Kotlin component managers own UIKit and Android widgets. The shared Yoga C++ engine computes layout beside the controls, using platform measurements for text and intrinsic sizes.
+- **Native widgets and layout:** Swift and Kotlin component managers own UIKit and Android widgets. The renderer core validates commits, lays out with Yoga off the UI thread using platform measurements for text and intrinsic sizes, and skips mounting layout-only wrappers.
 - **Standard asyncio:** Components, effects, event handlers, and tasks run on a dedicated Python application thread. Native UI threads handle widgets, scrolling, and animation frames. Component-owned tasks are canceled on unmount.
 - **Incremental reconciliation:** State changes update affected component subtrees. Versioned bridge commits validate operations and acknowledge revisions; events and controlled text inputs carry identities that prevent stale updates.
 - **Typed, Pythonic authoring:** Components return `pn.Node` and their signatures are their props, so a strict type checker verifies element trees and conditional children. Screens are components whose parameters are their route params (`nav.push(ItemScreen(id=42))`), navigators are module-level values with deep links derived from each screen's `path`, one `Theme` dataclass styles the app and its navigators, `StyleSheet` namespaces give styles typed names, and `pn.Store` holds app state with selector-based re-renders. `pn lint` checks the rules of hooks.
 - **Native lists and navigation:** UIKit collection views and Android recycler views recycle cells for fixed or variable row sizes, grids, sections, and horizontal lists. Native navigation containers present logical screen roots at every nesting level while providers and component state remain in the shared Python tree; navigators take screen options, groups, tab-bar styles, and a navigation ref usable outside components.
-- **Animation and gestures:** Serialized animation graphs support timing with named or bezier easing, springs, React Native's decay model, arithmetic, interpolation, and native scroll and gesture bindings. Swift and Kotlin recognize mobile gestures with Gesture Handler-style activation offsets and update supported animation bindings without Python work on every frame.
+- **Animation and gestures:** Serialized animation graphs support timing with named or bezier easing, springs, React Native's decay model, arithmetic, interpolation, and native scroll and gesture bindings. Gestures activate with Gesture Handler-style offsets and update supported animation bindings without Python work on every frame.
 - **Assets and graphics:** Drop images, fonts, and SVGs under `app/assets/` and reference them by path. Density variants, bundled fonts, a vector `Icon` set, `Svg` drawing, gradients, and blur render natively on both platforms and in the browser preview.
 - **Device APIs:** Python facades expose camera, location, notifications, storage, permissions, keyboard, dimensions and pixel ratio, device info, localization, accessibility settings, and other native services, with a Python fallback for headless tests. Test permissions and platform behavior on your deployment targets.
 - **Native extension SDK:** Python dataclasses and protocols define contracts; `define_component` returns a typed element factory and `pn codegen` generates props and module adapters for Swift and Kotlin. Plugins package native sources and resources, and builds verify matching contracts at startup.
@@ -45,7 +45,7 @@ PythonNative is a cross-platform toolkit for building native Android and iOS app
 - **PythonNative Go:** a prebuilt dev client, published with each release, runs any project without native code, so the project itself is never compiled. `i` / `a` in `pn start` open it on the iOS Simulator (which still needs Xcode installed) or an Android emulator, and a phone with Go installed opens the project by scanning the QR code `pn start` prints. Go isn't in the app stores: Android phones install the APK, and iPhones need Go built and signed with your Apple team. Projects that add native code run in their own debug build, which `pn run` rebuilds only when something native changes.
 - **DevTools and debugging:** `pn start` serves DevTools, with a component tree showing props and hooks (and editable state), a console with a REPL inside the running app, problems with component stacks and source excerpts, network requests, and live performance with trace capture. VS Code attaches `debugpy` breakpoints to Python on the preview, a simulator, or a phone. On device, a dev menu (shake or Cmd+D) offers reload, an element inspector, and a performance monitor, and errors show a screen with the component stack and your source.
 - **Development tools:** Fast Refresh preserves compatible component state, `pn lint` checks the rules of hooks, and `pn init` scaffolds tests, type checking, debugger settings, and CI.
-- **Browser preview:** `pn preview` runs your Python application against a browser renderer with DOM widgets, Yoga WebAssembly layout, and JavaScript animation graphs. It supports iteration on application logic and UI; fonts, platform controls, and device APIs require mobile testing.
+- **Browser preview:** `pn preview` runs your Python application against DOM widgets mounted by the same renderer core, compiled to WebAssembly. It supports iteration on application logic and UI; fonts, platform controls, and device APIs require mobile testing.
 - **App packaging and dependency locks:** `pn run` and `pn build` stage bundled app templates, native libraries, and Python sources. Target-specific wheel locks record dependency versions and hashes for mobile builds. Binary dependencies need compatible mobile wheels; `pn deps` reports target resolution.
 
 ## Quick Start

{pythonnative-0.50.0 → pythonnative-0.52.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pythonnative"
-version = "0.50.0"
+version = "0.52.0"
 description = "Cross-platform native UI toolkit for Android and iOS"
 authors = [
   { name = "Owen Carey" }

{pythonnative-0.50.0 → pythonnative-0.52.0}/scripts/check-distributions.py

@@ -18,12 +18,16 @@ PYTHONS = {"cp313", "cp314"}
 PLATFORMS = {"linux_x86_64", "linux_aarch64", "macos_x86_64", "macos_arm64", "win_amd64"}
 PACKAGE_FILES = {
     "pythonnative/py.typed",
-    "pythonnative/native/yoga/python.cpp",
-    "pythonnative/native/yoga/yoga/Yoga.h",
-    "pythonnative/native/yoga/yoga/YGNode.cpp",
+    "pythonnative/native/core/python.cpp",
+    "pythonnative/native/core/include/pn_core.h",
+    "pythonnative/native/core/src/core.cpp",
+    "pythonnative/native/core/yoga/Yoga.h",
+    "pythonnative/native/core/yoga/YGNode.cpp",
     "pythonnative/native/ios/Package.swift",
     "pythonnative/templates/android_template/gradlew",
-    "pythonnative/devserver/static/yoga/binaries/yoga-wasm-base64-esm.js",
+    "pythonnative/devserver/static/core/mount.js",
+    "pythonnative/devserver/static/core/pn_core.js",
+    "pythonnative/devserver/static/core/pn_core.wasm",
 }
 
 
@@ -77,8 +81,8 @@ def check_distributions(directory: Path, expected_version: str) -> None:
                 if wheel.get("Root-Is-Purelib") != "false" or archive_tags != tags:
                     raise ValueError(f"Wheel metadata disagrees with binary platform tags: {path.name}")
                 suffix = ".pyd" if next(iter(targets))[1] == "win_amd64" else ".so"
-                if not any(n.startswith("pythonnative/_yoga.") and n.endswith(suffix) for n in names):
-                    raise ValueError(f"Missing compiled Yoga extension: {path.name}")
+                if not any(n.startswith("pythonnative/_core.") and n.endswith(suffix) for n in names):
+                    raise ValueError(f"Missing compiled renderer core: {path.name}")
                 missing = PACKAGE_FILES - names
                 if missing:
                     raise ValueError(f"Missing package resources in {path.name}: {sorted(missing)}")
@@ -91,7 +95,11 @@ def check_distributions(directory: Path, expected_version: str) -> None:
                 prefix = f"pythonnative-{version}/"
                 names = set(archive.getnames())
                 required = {prefix + "src/" + name for name in PACKAGE_FILES}
-                required |= {prefix + "setup.py", prefix + "tests/test_layout.py"}
+                required |= {
+                    prefix + "setup.py",
+                    prefix + "tests/test_core.py",
+                    prefix + "tests/contracts/validation.json",
+                }
                 if missing := required - names:
                     raise ValueError(f"Incomplete source distribution: {sorted(missing)}")
                 metadata_file = archive.extractfile(prefix + "PKG-INFO")

{pythonnative-0.50.0 → pythonnative-0.52.0}/scripts/cibuildwheel.toml

@@ -5,12 +5,13 @@ build = ["cp313-*", "cp314-*"]
 skip = ["*-musllinux*", "*-win32", "*-manylinux_i686"]
 archs = ["native"]
 test-requires = ["pytest>=8"]
-# Install the repaired wheel into a fresh environment and copy just this
-# test file to a temporary directory, outside the source checkout.
-test-sources = ["tests/test_layout.py"]
+# Install the repaired wheel into a fresh environment and copy just the
+# renderer core's tests and their fixtures to a temporary directory,
+# outside the source checkout.
+test-sources = ["tests/test_core.py", "tests/contracts"]
 test-command = [
   "python -c \"import pythonnative; from importlib.metadata import version; from pathlib import Path; assert 'site-packages' in Path(pythonnative.__file__).parts; assert pythonnative.__version__ == version('pythonnative')\"",
-  "python -m pytest -q tests/test_layout.py",
+  "python -m pytest -q tests/test_core.py",
   "pn --help",
 ]
 
@@ -21,7 +22,3 @@ manylinux-aarch64-image = "manylinux_2_28"
 [tool.cibuildwheel.macos]
 environment = { MACOSX_DEPLOYMENT_TARGET = "11.0" }
 
-[tool.cibuildwheel.windows]
-# These flags also make v0.40.0's C API available to ctypes without patching
-# the tagged source. setup.py supplies them for future source builds.
-environment = { CL = "/D_WINDLL", LINK = "/EXPORT:pn_yoga_callback /EXPORT:pn_yoga_measure" }

pythonnative-0.52.0/setup.py

@@ -0,0 +1,23 @@
+"""Build the host renderer core; mobile hosts compile the same sources."""
+
+import os
+from pathlib import Path
+
+from setuptools import Extension, setup
+
+root = Path("src/pythonnative/native/core")
+sources = [root / "python.cpp", *sorted((root / "src").glob("*.cpp")), *sorted((root / "yoga").rglob("*.cpp"))]
+setup(
+    ext_modules=[
+        Extension(
+            "pythonnative._core",
+            sources=[str(path) for path in sources],
+            include_dirs=[str(root), str(root / "include")],
+            language="c++",
+            extra_compile_args=["/std:c++20"] if os.name == "nt" else ["-std=c++20", "-fvisibility=hidden"],
+            # ctypes loads the core's C ABI (exported with PN_CORE_API) from
+            # the extension library, not just Python's module initializer.
+            define_macros=[("_WINDLL", "1")] if os.name == "nt" else [],
+        )
+    ]
+)

{pythonnative-0.50.0 → pythonnative-0.52.0}/src/pythonnative/__init__.py

@@ -66,7 +66,7 @@ Example:
     ```
 """
 
-__version__ = "0.50.0"
+__version__ = "0.52.0"
 
 import importlib
 from typing import TYPE_CHECKING, Any