pythonhere 0.3.0__tar.gz → 0.3.1__tar.gz

{pythonhere-0.3.0/pythonhere.egg-info → pythonhere-0.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythonhere
-Version: 0.3.0
+Version: 0.3.1
 Summary: Here is the Kivy based app to run code from the Jupyter magic %there
 Author-email: b3b <ash.b3b@gmail.com>
 License-Expression: MIT
@@ -16,7 +16,7 @@ Classifier: Programming Language :: Python :: 3.14
 Requires-Python: >=3.10
 Description-Content-Type: text/x-rst
 License-File: LICENSE
-Requires-Dist: herethere[magic]>=0.3.1
+Requires-Dist: herethere[magic]>=0.3.2
 Requires-Dist: ipython
 Requires-Dist: ipywidgets
 Requires-Dist: Pillow

{pythonhere-0.3.0 → pythonhere-0.3.1}/pyproject.toml

@@ -22,7 +22,7 @@ classifiers = [
     "Programming Language :: Python :: 3.14",
 ]
 dependencies = [
-    "herethere[magic]>=0.3.1",
+    "herethere[magic]>=0.3.2",
     "ipython",
     "ipywidgets",
     "Pillow",

{pythonhere-0.3.0 → pythonhere-0.3.1}/pythonhere/.agents/skills/pythonhere/SKILL.md

@@ -66,9 +66,11 @@ They complement rather than restrict normal Python:
 These helpers may be called on Kivy's main thread or from a worker. Worker calls
 are transparently marshaled to Kivy's thread and block that worker until Kivy
 finishes the operation, normally on its next frame. Continue to prefer normal
-foreground `there get` and `there run` for quick UI operations. Background
-execution is useful when surrounding work would otherwise block the UI; it does
-not make other Kivy access thread-safe.
+foreground `there get` and `there run` for quick UI operations. Add `--worker`
+to `get` or `run` when surrounding slow or blocking work would otherwise block
+the UI. The CLI remains attached, waits for completion, and then returns the
+value or captured output. Worker execution does not make other Kivy access
+thread-safe.
 
 Do not call a worker-marshaled helper while Kivy's main thread is synchronously
 waiting for that same worker. Neither side can progress in that cross-thread
@@ -179,7 +181,9 @@ there --json run --code "from tools_here import pin_shortcut; pin_shortcut('demo
    - Keep callbacks non-blocking and marshal UI changes to the Kivy thread.
 4. For more than a short expression, create a local UTF-8 Python file and run it
    with `there --json run FILE`. Prefer a file over fragile shell quoting or a
-   long `--code` value. Keep within the installed CLI's input limit.
+   long `--code` value. Keep within the installed CLI's input limit. Add
+   `--worker` for slow or blocking code that should not occupy Kivy's main
+   thread.
 5. Make only the requested live-app mutation. Reuse existing state when
    practical and provide cleanup helpers for scheduled events, sensors,
    Bluetooth, MIDI, files, or other held resources.
@@ -223,6 +227,13 @@ Run a prepared UI change:
 there --json run /tmp/pythonhere-ui.py
 ```
 
+Run slow or blocking non-UI work without freezing Kivy, while waiting for its
+buffered output:
+
+```console
+there --json run --worker /tmp/pythonhere-long-task.py
+```
+
 Verify a named status left by that code:
 
 ```console

pythonhere-0.3.1/pythonhere/version_here.py

@@ -0,0 +1 @@
+__version__ = "0.3.1"

{pythonhere-0.3.0 → pythonhere-0.3.1/pythonhere.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythonhere
-Version: 0.3.0
+Version: 0.3.1
 Summary: Here is the Kivy based app to run code from the Jupyter magic %there
 Author-email: b3b <ash.b3b@gmail.com>
 License-Expression: MIT
@@ -16,7 +16,7 @@ Classifier: Programming Language :: Python :: 3.14
 Requires-Python: >=3.10
 Description-Content-Type: text/x-rst
 License-File: LICENSE
-Requires-Dist: herethere[magic]>=0.3.1
+Requires-Dist: herethere[magic]>=0.3.2
 Requires-Dist: ipython
 Requires-Dist: ipywidgets
 Requires-Dist: Pillow

{pythonhere-0.3.0 → pythonhere-0.3.1}/pythonhere.egg-info/requires.txt

@@ -1,4 +1,4 @@
-herethere[magic]>=0.3.1
+herethere[magic]>=0.3.2
 ipython
 ipywidgets
 Pillow

{pythonhere-0.3.0 → pythonhere-0.3.1}/tests/test_main.py

@@ -111,7 +111,7 @@ async def test_root_object_is_in_context(capfd, app_instance, there):
 
 
 @pytest.mark.asyncio
-async def test_background_snapshot_traverses_widgets_on_main_thread(
+async def test_worker_snapshot_traverses_widgets_on_main_thread(
     app_instance,
     there,
 ):
@@ -129,18 +129,8 @@ async def test_background_snapshot_traverses_widgets_on_main_thread(
         )
     )
     try:
-        if hasattr(there, "get_background"):
-            snapshot = await there.get_background("tools_here.snapshot_ui(root)")
-            runtime = await there.get_background("tools_here.runtime_info(app, root)")
-        else:
-            # Herethere 0.3.0 has background execution but predates its
-            # background value command. Exercise the same worker bridge while
-            # keeping this integration test compatible with that release.
-            await there.runcode_background(
-                "tools_here._test_background_results = "
-                "(tools_here.snapshot_ui(root), tools_here.runtime_info(app, root))"
-            )
-            snapshot, runtime = await there.get("tools_here._test_background_results")
+        snapshot = await there.get_worker("tools_here.snapshot_ui(root)")
+        runtime = await there.get_worker("tools_here.runtime_info(app, root)")
         ran_on_main_thread = await there.get(
             "tools_here._test_snapshot_thread == "
             "__import__('threading').main_thread().ident"

pythonhere-0.3.0/pythonhere/version_here.py

@@ -1 +0,0 @@
-__version__ = "0.3.0"