pythonnative 0.9.0__py3-none-any.whl → 0.11.0__py3-none-any.whl

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/_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/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]`).
+"""