pythonnative 0.9.0__tar.gz → 0.11.0__tar.gz

{pythonnative-0.9.0/src/pythonnative.egg-info → pythonnative-0.11.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythonnative
-Version: 0.9.0
+Version: 0.11.0
 Summary: Cross-platform native UI toolkit for Android and iOS
 Author: Owen Carey
 License: MIT License
@@ -48,6 +48,8 @@ Provides-Extra: docs
 Requires-Dist: mkdocs>=1.5; extra == "docs"
 Requires-Dist: mkdocs-material[imaging]>=9.5; extra == "docs"
 Requires-Dist: mkdocstrings[python]>=0.24; extra == "docs"
+Requires-Dist: mkdocs-autorefs>=1.0; extra == "docs"
+Requires-Dist: pymdown-extensions>=10.7; extra == "docs"
 Provides-Extra: dev
 Requires-Dist: black>=24.0; extra == "dev"
 Requires-Dist: ruff>=0.5; extra == "dev"
@@ -95,6 +97,7 @@ PythonNative is a cross-platform toolkit for building native Android and iOS app
 - **Declarative UI:** Describe *what* your UI should look like with element functions (`Text`, `Button`, `Column`, `Row`, etc.). PythonNative creates and updates native views automatically.
 - **Hooks and function components:** Manage state with `use_state`, side effects with `use_effect`, and navigation with `use_navigation`, all through one consistent pattern.
 - **`style` prop:** Pass all visual and layout properties through a single `style` dict, composable via `StyleSheet`.
+- **Cross-platform flexbox engine:** A pure-Python, Yoga-style layout engine computes frames once and applies them to native views, so `flex`, `padding`, `aspect_ratio`, and `position: "absolute"` produce the same geometry on Android and iOS.
 - **Virtual view tree + reconciler:** Element trees are diffed and patched with minimal native mutations, similar to React's reconciliation.
 - **Direct native bindings:** Python calls platform APIs directly through Chaquopy and rubicon-objc, with no JavaScript bridge.
 - **CLI scaffolding:** `pn init` creates a ready-to-run project; `pn run android` and `pn run ios` build and launch your app.

{pythonnative-0.9.0 → pythonnative-0.11.0}/README.md

@@ -33,6 +33,7 @@ PythonNative is a cross-platform toolkit for building native Android and iOS app
 - **Declarative UI:** Describe *what* your UI should look like with element functions (`Text`, `Button`, `Column`, `Row`, etc.). PythonNative creates and updates native views automatically.
 - **Hooks and function components:** Manage state with `use_state`, side effects with `use_effect`, and navigation with `use_navigation`, all through one consistent pattern.
 - **`style` prop:** Pass all visual and layout properties through a single `style` dict, composable via `StyleSheet`.
+- **Cross-platform flexbox engine:** A pure-Python, Yoga-style layout engine computes frames once and applies them to native views, so `flex`, `padding`, `aspect_ratio`, and `position: "absolute"` produce the same geometry on Android and iOS.
 - **Virtual view tree + reconciler:** Element trees are diffed and patched with minimal native mutations, similar to React's reconciliation.
 - **Direct native bindings:** Python calls platform APIs directly through Chaquopy and rubicon-objc, with no JavaScript bridge.
 - **CLI scaffolding:** `pn init` creates a ready-to-run project; `pn run android` and `pn run ios` build and launch your app.

{pythonnative-0.9.0 → pythonnative-0.11.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pythonnative"
-version = "0.9.0"
+version = "0.11.0"
 description = "Cross-platform native UI toolkit for Android and iOS"
 authors = [
   { name = "Owen Carey" }
@@ -35,6 +35,8 @@ docs = [
   "mkdocs>=1.5",
   "mkdocs-material[imaging]>=9.5",
   "mkdocstrings[python]>=0.24",
+  "mkdocs-autorefs>=1.0",
+  "pymdown-extensions>=10.7",
 ]
 dev = [
   "black>=24.0",
@@ -81,8 +83,32 @@ extend-exclude = [
 ]
 
 [tool.ruff.lint]
-select = ["E", "F", "I"]
-ignore = []
+# Docstring (D) rules use the Google convention; see [tool.ruff.lint.pydocstyle].
+# Selectively enabled so tests/examples/templates aren't penalized.
+select = ["E", "F", "I", "D"]
+# D107 (missing __init__ docstring): mkdocstrings is configured to merge
+#   __init__ into the class docstring, so the class docstring is the source of truth.
+# D105 (magic method docstring): most are self-explanatory (__repr__, __eq__, etc.).
+# D203/D213: conflict with Google convention defaults; ruff auto-suppresses
+#   these via `convention = "google"`, but we list them defensively.
+ignore = ["D107", "D105", "D203", "D213"]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**/*.py" = ["D"]
+"examples/**/*.py" = ["D"]
+"src/pythonnative/templates/**/*.py" = ["D"]
+"setup.py" = ["D"]
+"conftest.py" = ["D"]
+# Platform handler subclasses implement the ViewHandler ABC defined in
+# native_views/base.py, which carries the canonical docstrings for the
+# protocol. The concrete classes are internal (registered by name in
+# NativeViewRegistry, never imported by users), so requiring per-method
+# docstrings would only add boilerplate that repeats the ABC.
+"src/pythonnative/native_views/android.py" = ["D101", "D102"]
+"src/pythonnative/native_views/ios.py" = ["D101", "D102"]
+
+[tool.ruff.lint.pydocstyle]
+convention = "google"
 
 [tool.black]
 line-length = 120

{pythonnative-0.9.0 → pythonnative-0.11.0}/src/pythonnative/__init__.py

@@ -1,7 +1,31 @@
-"""PythonNative — declarative native UI for Android and iOS.
+"""PythonNative: declarative native UI for Android and iOS.
 
-Public API::
+PythonNative is a cross-platform toolkit that turns Python ``@component``
+functions into real, native Android and iOS views. The component model
+is React-like (function components plus hooks), but rendering happens
+through direct platform bindings: Chaquopy on Android (Java) and
+rubicon-objc on iOS (Objective-C). There is no JavaScript bridge.
 
+Key building blocks:
+
+- **Element factories** ([`Text`][pythonnative.Text],
+  [`Button`][pythonnative.Button], [`Column`][pythonnative.Column], etc.)
+  return immutable [`Element`][pythonnative.Element] descriptors.
+- **Hooks** ([`use_state`][pythonnative.use_state],
+  [`use_effect`][pythonnative.use_effect],
+  [`use_reducer`][pythonnative.use_reducer], etc.) manage state, side
+  effects, and context inside `@component` functions.
+- **Navigation** is built from
+  [`NavigationContainer`][pythonnative.NavigationContainer] plus one of
+  the [`create_stack_navigator`][pythonnative.create_stack_navigator],
+  [`create_tab_navigator`][pythonnative.create_tab_navigator], or
+  [`create_drawer_navigator`][pythonnative.create_drawer_navigator]
+  factories.
+- **Styling** uses a single ``style`` dict per element (or a list of
+  dicts), composable via [`StyleSheet`][pythonnative.StyleSheet].
+
+Example:
+    ```python
     import pythonnative as pn
 
     @pn.component
@@ -12,9 +36,10 @@ Public API::
             pn.Button("+", on_click=lambda: set_count(count + 1)),
             style={"spacing": 12},
         )
+    ```
 """
 
-__version__ = "0.9.0"
+__version__ = "0.11.0"
 
 from .components import (
     ActivityIndicator,

{pythonnative-0.9.0 → pythonnative-0.11.0}/src/pythonnative/_ios_log.py

@@ -1,24 +1,22 @@
-"""Route Python ``sys.stdout``/``sys.stderr`` through fd 2 on iOS.
-
-Why
----
-When an app is launched via ``xcrun simctl launch --console-pty`` (what
-``pn run ios`` does), the simulator attaches the caller's terminal to
-the app's stderr, which is the same channel ``NSLog`` / ``os_log``
-writes to. Python ``print()`` calls, however, go to ``sys.stdout``
-(fd 1), and for reasons specific to how CPython's embedded framework
-is started on the iOS Simulator that descriptor does not reach the
-attached console. As a result users see Swift-side ``NSLog`` output
-but never their own ``print()`` output.
-
-Redirecting ``sys.stdout`` / ``sys.stderr`` at a Python level to write
+"""Route Python `sys.stdout`/`sys.stderr` through fd 2 on iOS.
+
+When an app is launched via `xcrun simctl launch --console-pty`
+(what `pn run ios` does), the simulator attaches the caller's
+terminal to the app's stderr, which is the same channel `NSLog` and
+`os_log` write to. Python `print()` calls, however, go to
+`sys.stdout` (fd 1), and for reasons specific to how CPython's
+embedded framework is started on the iOS Simulator that descriptor
+does not reach the attached console. As a result, users see
+Swift-side `NSLog` output but never their own `print()` output.
+
+Redirecting `sys.stdout` and `sys.stderr` at a Python level to write
 straight to fd 2 is a small, reliable fix: fd 2 *is* visible to
-``simctl`` (that's exactly how ``NSLog`` reaches the terminal), so
+`simctl` (that is exactly how `NSLog` reaches the terminal), so
 Python output lands next to the Swift logs with correct ordering.
 
-This module is intentionally self-contained: no rubicon-objc or
-platform-specific C bindings required, so it's safe to import early
-during ``pythonnative`` package initialization.
+This module is intentionally self-contained (no rubicon-objc or
+platform-specific C bindings required), so it is safe to import
+early during `pythonnative` package initialization.
 """
 
 from __future__ import annotations
@@ -33,8 +31,8 @@ _STDERR_FD = 2
 class _StderrStream:
     """Minimal text-mode file-like that writes UTF-8 bytes to fd 2.
 
-    It's write-through (no buffering) so a ``print()`` call appears in
-    the terminal immediately, which matches user expectations for an
+    Write-through (no buffering), so a `print()` call appears in the
+    terminal immediately. That matches user expectations for an
     interactive "run on simulator" log stream.
     """
 
@@ -82,9 +80,9 @@ _installed = False
 
 
 def install() -> None:
-    """Swap ``sys.stdout`` / ``sys.stderr`` for fd-2 writers.
+    """Swap `sys.stdout` and `sys.stderr` for fd-2 writers.
 
-    Safe to call multiple times; only the first call has effect.
+    Idempotent: only the first call has effect.
     """
     global _installed
     if _installed:

pythonnative-0.11.0/src/pythonnative/cli/__init__.py

@@ -0,0 +1,7 @@
+"""Command-line interface package for the `pn` script.
+
+The CLI entry point lives in
+[`pythonnative.cli.pn`][pythonnative.cli.pn] and is exposed as the
+`pn` console script (configured in `pyproject.toml`'s
+`[project.scripts]`).
+"""