microio 0.1.0__tar.gz

microio-0.1.0/CHANGELOG.md

@@ -0,0 +1,6 @@
+<!-- do not remove -->
+
+## 0.1.0
+
+- Init release
+

microio-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

microio-0.1.0/MANIFEST.in

@@ -0,0 +1,4 @@
+include README.md
+include LICENSE
+include CHANGELOG.md
+recursive-include examples *.md *.py

microio-0.1.0/PKG-INFO

@@ -0,0 +1,241 @@
+Metadata-Version: 2.4
+Name: microio
+Version: 0.1.0
+Summary: Tiny asyncio-first runtime helpers for service threads, loop ownership, channels, and request waiters
+Author: microio contributors
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/AnswerDotAI/microio
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: fastship; extra == "dev"
+Requires-Dist: build; extra == "dev"
+Requires-Dist: twine; extra == "dev"
+Requires-Dist: pytest; extra == "dev"
+Dynamic: license-file
+
+# microio
+
+`microio` is a tiny asyncio-first runtime helper library for services that own
+event loops, sockets, background threads, and request/reply waiters.
+
+It is inspired by AnyIO's practical concurrency ideas, especially the problems
+called out in [Why you should be using AnyIO APIs instead of asyncio APIs][anyio-why]:
+
+- **task readiness**: a child service should be able to report "ready" or "failed"
+  before its parent continues;
+- **cancel scopes**: stopping is a durable state with a reason, not a one-shot flag
+  that individual operations may miss;
+- **memory object streams**: producers and consumers should be split into explicit
+  sender/receiver endpoints with clear close semantics;
+- **thread bridges**: code outside an event-loop thread needs a safe way to submit
+  work into that loop and observe failures.
+
+`microio` is not a compatibility layer over asyncio, Trio, and Curio. It is also
+not a reimplementation of AnyIO. It intentionally stays smaller:
+
+- asyncio only;
+- stdlib only;
+- no generic networking/file APIs;
+- cooperative level cancellation only where code uses `microio` scopes and checkpoints;
+- no pytest plugin or framework-level dependency injection.
+
+The goal is to make the common "small service runtime" patterns reliable and
+testable without pulling a full concurrency abstraction into projects that already
+use asyncio directly.
+
+## What It Provides
+
+### `TaskGroup` / `CancelScope`
+
+`create_task_group()` wraps `asyncio.TaskGroup`. It keeps the stdlib failure
+rules, and adds the missing cancellation/readiness pieces:
+
+- `tg.start_soon(fn, *args)` starts a child task;
+- `await tg.start(fn, *args)` starts a child and waits until it calls
+  `task_status.started(value)`;
+- `tg.cancel_scope.cancel()` or `tg.cancel()` cancels owned tasks and treats
+  that as normal shutdown;
+- `checkpoint()`, `checkpoint_if_cancelled()`, and `sleep()` provide cooperative
+  level cancellation for code that uses `microio` primitives;
+- `move_on_after(seconds)` suppresses deadline cancellation;
+- `fail_after(seconds)` turns deadline cancellation into `TimeoutError`.
+
+The group-cancel path borrows the small `asyncio_cancel_scope` trick: when a
+child task or another thread asks a group to stop, `microio` injects a private
+task exception into the underlying `asyncio.TaskGroup` and suppresses just that
+private exception on exit.
+
+This is still asyncio cancellation. Raw `await something()` follows asyncio's
+edge-cancellation rules. Once code returns to a `microio` checkpoint, cancelled
+scopes keep raising `CancelledError`, even if earlier cancellation was caught.
+
+Shielding is not exposed. A partial shield around raw `Task.cancel()` would look
+stronger than it is.
+
+```python
+from microio import create_task_group, sleep
+
+
+async def worker():
+    while True: await sleep(1)
+
+
+async with create_task_group() as tg:
+    tg.start_soon(worker)
+    await sleep(0.1)
+    tg.cancel()
+```
+
+### `CloseScope`
+
+`CloseScope` is a small, thread-safe stop/failure state object. It records whether
+a service is closing, why it is closing, and whether there is an exception that
+should be propagated to waiters.
+
+This is separate from `CancelScope`. `CloseScope` is for thread-safe service
+lifecycle state. It does not cancel asyncio tasks for you.
+
+### `ServiceThread` / `ServiceGroup`
+
+`ServiceThread` is a supervised `threading.Thread`:
+
+- child code calls `started()` after resources are ready;
+- parents call `wait_started()` and get either readiness or the startup exception;
+- `stop()` marks the thread's `CloseScope`;
+- `join_or_log()` checks timeout results instead of ignoring them.
+
+Use it for socket threads, protocol readers, and other owned background services.
+
+`ServiceGroup` owns the repeated lifecycle boilerplate for a small set of service
+threads:
+
+```python
+services = ServiceGroup(iopub, stdin, heartbeat).start().wait_started()
+...
+services.stop_join(timeout=1)
+```
+
+### `LoopServiceThread`
+
+`LoopServiceThread` owns an `asyncio.Runner` inside a thread and exposes:
+
+- `call_soon()` for thread-safe callbacks;
+- `call_sync()` for thread-safe callbacks with a return value;
+- `submit()` for coroutine submission from other threads;
+- `task_group` for async work owned by the service;
+- the same ready/failed/stop/join behavior as `ServiceThread`.
+
+This is the small subset of AnyIO's thread-bridge idea that asyncio services often
+need: create one loop in one thread, keep ownership clear, submit coroutine work
+safely, and synchronously run small functions on the loop thread when needed.
+`stop()` cancels the service task group, so owned child tasks shut down with the
+service.
+
+### `ObjectChannel`
+
+`create_channel()` returns `(send, receive)` endpoints. A sender can be used from
+other threads before or after the receiver has bound to an event loop. The receiver
+is async and supports `async for`.
+
+This is inspired by AnyIO memory object streams, but adjusted for service threads:
+
+- the default buffer is unbounded because cross-thread producers often cannot
+  await backpressure;
+- close is explicit and wakes async receivers;
+- receivers raise `EndOfStream` on direct receive after close;
+- `fail(exc)` is explicit and wakes async receivers with the exception;
+- late sends raise `ClosedResourceError` unless `late_send="drop"` is selected;
+- the implementation is intentionally single-receiver and simple.
+
+### `Mailbox` / `ActorCore`
+
+`Mailbox` wraps an `ObjectChannel` for the common actor shape: thread-safe
+`submit()`, async receive, `close()`, `fail()`, and `drain_nowait()`.
+
+`ActorCore` is the tiny serialized consumer loop:
+
+```python
+actor = ActorCore(handle)
+actor.submit(item)
+await actor.run()
+```
+
+It is deliberately not tied to a thread. A service thread, a main-thread runner,
+or a test can all run the same actor core.
+
+### `RequestRegistry`
+
+`RequestRegistry` tracks request IDs and waiters:
+
+- register a request;
+- resolve it from another thread through a `ReplyHandle`;
+- wait with timeout;
+- wrap the common register-send-wait pattern with `request(key, send)`;
+- fail one or all pending requests on service crash/close.
+
+This is useful for debug adapters, stdin routers, RPC clients, and any protocol
+where a reader thread must wake request waiters reliably.
+
+## Example
+
+```python
+import asyncio
+from microio import LoopServiceThread, create_channel
+
+
+class Worker(LoopServiceThread):
+    def __init__(self):
+        super().__init__(name="worker")
+        self.send, self.receive = create_channel()
+
+    async def run_async(self):
+        self.receive.bind(asyncio.get_running_loop())
+        self.started()
+        async for item in self.receive:
+            if item == "stop":
+                self.stop()
+                break
+            print(item)
+
+
+worker = Worker()
+worker.start()
+worker.wait_started()
+worker.send.send_nowait("hello")
+worker.send.send_nowait("stop")
+worker.join_or_log(timeout=1)
+```
+
+## Design Rules
+
+- Prefer explicit state over hidden magic.
+- Make startup failure visible to the parent.
+- Never ignore a join timeout.
+- Waking pending waiters on close/crash is part of the service contract.
+- Keep asyncio ownership clear: a socket or loop belongs to one service thread.
+
+## Development
+
+```bash
+pip install -e .[dev]
+pytest -q
+```
+
+## Examples
+
+Run the counter service example:
+
+```bash
+python examples/counter_server.py
+```
+
+It shows `LoopServiceThread`, `ObjectChannel`, `RequestRegistry`, and
+`CloseScope` working together in one small service.
+
+Version lives in `microio/__init__.py` as `__version__`.
+
+[anyio-why]: https://anyio.readthedocs.io/en/stable/why.html

microio-0.1.0/README.md

@@ -0,0 +1,222 @@
+# microio
+
+`microio` is a tiny asyncio-first runtime helper library for services that own
+event loops, sockets, background threads, and request/reply waiters.
+
+It is inspired by AnyIO's practical concurrency ideas, especially the problems
+called out in [Why you should be using AnyIO APIs instead of asyncio APIs][anyio-why]:
+
+- **task readiness**: a child service should be able to report "ready" or "failed"
+  before its parent continues;
+- **cancel scopes**: stopping is a durable state with a reason, not a one-shot flag
+  that individual operations may miss;
+- **memory object streams**: producers and consumers should be split into explicit
+  sender/receiver endpoints with clear close semantics;
+- **thread bridges**: code outside an event-loop thread needs a safe way to submit
+  work into that loop and observe failures.
+
+`microio` is not a compatibility layer over asyncio, Trio, and Curio. It is also
+not a reimplementation of AnyIO. It intentionally stays smaller:
+
+- asyncio only;
+- stdlib only;
+- no generic networking/file APIs;
+- cooperative level cancellation only where code uses `microio` scopes and checkpoints;
+- no pytest plugin or framework-level dependency injection.
+
+The goal is to make the common "small service runtime" patterns reliable and
+testable without pulling a full concurrency abstraction into projects that already
+use asyncio directly.
+
+## What It Provides
+
+### `TaskGroup` / `CancelScope`
+
+`create_task_group()` wraps `asyncio.TaskGroup`. It keeps the stdlib failure
+rules, and adds the missing cancellation/readiness pieces:
+
+- `tg.start_soon(fn, *args)` starts a child task;
+- `await tg.start(fn, *args)` starts a child and waits until it calls
+  `task_status.started(value)`;
+- `tg.cancel_scope.cancel()` or `tg.cancel()` cancels owned tasks and treats
+  that as normal shutdown;
+- `checkpoint()`, `checkpoint_if_cancelled()`, and `sleep()` provide cooperative
+  level cancellation for code that uses `microio` primitives;
+- `move_on_after(seconds)` suppresses deadline cancellation;
+- `fail_after(seconds)` turns deadline cancellation into `TimeoutError`.
+
+The group-cancel path borrows the small `asyncio_cancel_scope` trick: when a
+child task or another thread asks a group to stop, `microio` injects a private
+task exception into the underlying `asyncio.TaskGroup` and suppresses just that
+private exception on exit.
+
+This is still asyncio cancellation. Raw `await something()` follows asyncio's
+edge-cancellation rules. Once code returns to a `microio` checkpoint, cancelled
+scopes keep raising `CancelledError`, even if earlier cancellation was caught.
+
+Shielding is not exposed. A partial shield around raw `Task.cancel()` would look
+stronger than it is.
+
+```python
+from microio import create_task_group, sleep
+
+
+async def worker():
+    while True: await sleep(1)
+
+
+async with create_task_group() as tg:
+    tg.start_soon(worker)
+    await sleep(0.1)
+    tg.cancel()
+```
+
+### `CloseScope`
+
+`CloseScope` is a small, thread-safe stop/failure state object. It records whether
+a service is closing, why it is closing, and whether there is an exception that
+should be propagated to waiters.
+
+This is separate from `CancelScope`. `CloseScope` is for thread-safe service
+lifecycle state. It does not cancel asyncio tasks for you.
+
+### `ServiceThread` / `ServiceGroup`
+
+`ServiceThread` is a supervised `threading.Thread`:
+
+- child code calls `started()` after resources are ready;
+- parents call `wait_started()` and get either readiness or the startup exception;
+- `stop()` marks the thread's `CloseScope`;
+- `join_or_log()` checks timeout results instead of ignoring them.
+
+Use it for socket threads, protocol readers, and other owned background services.
+
+`ServiceGroup` owns the repeated lifecycle boilerplate for a small set of service
+threads:
+
+```python
+services = ServiceGroup(iopub, stdin, heartbeat).start().wait_started()
+...
+services.stop_join(timeout=1)
+```
+
+### `LoopServiceThread`
+
+`LoopServiceThread` owns an `asyncio.Runner` inside a thread and exposes:
+
+- `call_soon()` for thread-safe callbacks;
+- `call_sync()` for thread-safe callbacks with a return value;
+- `submit()` for coroutine submission from other threads;
+- `task_group` for async work owned by the service;
+- the same ready/failed/stop/join behavior as `ServiceThread`.
+
+This is the small subset of AnyIO's thread-bridge idea that asyncio services often
+need: create one loop in one thread, keep ownership clear, submit coroutine work
+safely, and synchronously run small functions on the loop thread when needed.
+`stop()` cancels the service task group, so owned child tasks shut down with the
+service.
+
+### `ObjectChannel`
+
+`create_channel()` returns `(send, receive)` endpoints. A sender can be used from
+other threads before or after the receiver has bound to an event loop. The receiver
+is async and supports `async for`.
+
+This is inspired by AnyIO memory object streams, but adjusted for service threads:
+
+- the default buffer is unbounded because cross-thread producers often cannot
+  await backpressure;
+- close is explicit and wakes async receivers;
+- receivers raise `EndOfStream` on direct receive after close;
+- `fail(exc)` is explicit and wakes async receivers with the exception;
+- late sends raise `ClosedResourceError` unless `late_send="drop"` is selected;
+- the implementation is intentionally single-receiver and simple.
+
+### `Mailbox` / `ActorCore`
+
+`Mailbox` wraps an `ObjectChannel` for the common actor shape: thread-safe
+`submit()`, async receive, `close()`, `fail()`, and `drain_nowait()`.
+
+`ActorCore` is the tiny serialized consumer loop:
+
+```python
+actor = ActorCore(handle)
+actor.submit(item)
+await actor.run()
+```
+
+It is deliberately not tied to a thread. A service thread, a main-thread runner,
+or a test can all run the same actor core.
+
+### `RequestRegistry`
+
+`RequestRegistry` tracks request IDs and waiters:
+
+- register a request;
+- resolve it from another thread through a `ReplyHandle`;
+- wait with timeout;
+- wrap the common register-send-wait pattern with `request(key, send)`;
+- fail one or all pending requests on service crash/close.
+
+This is useful for debug adapters, stdin routers, RPC clients, and any protocol
+where a reader thread must wake request waiters reliably.
+
+## Example
+
+```python
+import asyncio
+from microio import LoopServiceThread, create_channel
+
+
+class Worker(LoopServiceThread):
+    def __init__(self):
+        super().__init__(name="worker")
+        self.send, self.receive = create_channel()
+
+    async def run_async(self):
+        self.receive.bind(asyncio.get_running_loop())
+        self.started()
+        async for item in self.receive:
+            if item == "stop":
+                self.stop()
+                break
+            print(item)
+
+
+worker = Worker()
+worker.start()
+worker.wait_started()
+worker.send.send_nowait("hello")
+worker.send.send_nowait("stop")
+worker.join_or_log(timeout=1)
+```
+
+## Design Rules
+
+- Prefer explicit state over hidden magic.
+- Make startup failure visible to the parent.
+- Never ignore a join timeout.
+- Waking pending waiters on close/crash is part of the service contract.
+- Keep asyncio ownership clear: a socket or loop belongs to one service thread.
+
+## Development
+
+```bash
+pip install -e .[dev]
+pytest -q
+```
+
+## Examples
+
+Run the counter service example:
+
+```bash
+python examples/counter_server.py
+```
+
+It shows `LoopServiceThread`, `ObjectChannel`, `RequestRegistry`, and
+`CloseScope` working together in one small service.
+
+Version lives in `microio/__init__.py` as `__version__`.
+
+[anyio-why]: https://anyio.readthedocs.io/en/stable/why.html

microio-0.1.0/examples/README.md

@@ -0,0 +1,13 @@
+# microio examples
+
+## Counter server
+
+Run from the `microio` project directory:
+
+```bash
+python examples/counter_server.py
+```
+
+The example starts a tiny in-process service. The main thread sends request
+objects through an `ObjectChannel` to a `LoopServiceThread`, waits for replies
+with a `RequestRegistry`, and shuts the service down through its `CloseScope`.