rsloop 0.1.1__tar.gz → 0.1.2__tar.gz

{rsloop-0.1.1 → rsloop-0.1.2}/.github/workflows/wheels.yml

@@ -19,8 +19,13 @@ jobs:
         include:
           - os_name: linux
             runner: ubuntu-latest
-          - os_name: macos
+            rust_target: x86_64-unknown-linux-gnu
+          - os_name: macos-intel
             runner: macos-15-intel
+            rust_target: x86_64-apple-darwin
+          - os_name: macos-arm64
+            runner: macos-15
+            rust_target: aarch64-apple-darwin
 
     steps:
       - name: Check out repository
@@ -45,7 +50,7 @@ jobs:
         uses: Swatinem/rust-cache@v2
 
       - name: Build wheels
-        run: scripts/build-wheels.sh --out dist
+        run: scripts/build-wheels.sh --out dist --target "${{ matrix.rust_target }}"
 
       - name: Upload wheel artifacts
         uses: actions/upload-artifact@v4

{rsloop-0.1.1 → rsloop-0.1.2}/LICENSE

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright [yyyy] [name of copyright owner]
+   Copyright 2026 Yehor Smoliakov
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

{rsloop-0.1.1 → rsloop-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rsloop
-Version: 0.1.1
+Version: 0.1.2
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: Apache Software License
@@ -32,16 +32,35 @@ Project-URL: Repository, https://github.com/RustedBytes/rsloop
 
 <img src="./rsloop.png" alt="rsloop logo" align="center">
 
-# `rsloop`: An event loop for asyncio written in Rust
+# An event loop for asyncio written in Rust
 
-`rsloop` is a PyO3-based `asyncio` event loop. Each `rsloop.Loop` still owns a
-dedicated Rust runtime thread for timers, readiness polling, signal watchers,
-and transport coordination, but Python callbacks, tasks, and coroutines are
-driven on the thread that calls `run_forever()` / `run_until_complete()`
-(typically the main thread). The package exposes a Python module at
+[![PyPI - Version](https://img.shields.io/pypi/v/rsloop)](https://pypi.org/project/rsloop/)
+[![PyPI Downloads](https://static.pepy.tech/personalized-badge/rsloop?period=total&units=INTERNATIONAL_SYSTEM&left_color=BLACK&right_color=GREEN&left_text=downloads)](https://pepy.tech/projects/rsloop)
+
+`rsloop` is a PyO3-based `asyncio` event loop. Each `rsloop.Loop` owns a
+dedicated Rust runtime thread that handles loop coordination and I/O-related
+runtime work, while Python callbacks, tasks, and coroutines are executed on
+the thread that calls `run_forever()` / `run_until_complete()` (typically the
+main thread). The package exposes a Python module at
 `rsloop._loop` plus a small Python wrapper in `python/rsloop/__init__.py`.
 
-The project metadata currently targets Python `>=3.8`.
+The project metadata currently targets Python `>=3.8`. The current
+implementation is Unix-focused and intended for Linux and macOS; Windows is
+not supported by this codebase.
+
+## Install
+
+Install the published package from PyPI:
+
+```bash
+pip install rsloop
+```
+
+With `uv`:
+
+```bash
+uv add rsloop
+```
 
 ## Current Surface Area
 
@@ -93,7 +112,8 @@ Today’s codebase provides:
   - `create_unix_connection`
   - `connect_accepted_socket`
   - returned `Server` and `StreamTransport` objects
-  - `transport.close()` / `transport.abort()` fully close socket transports
+  - `transport.close()` / `transport.abort()` are implemented for socket
+    transports
 - pipe transports:
   - `connect_read_pipe`
   - `connect_write_pipe`
@@ -145,6 +165,12 @@ level transport implementation lives in `src/stream_transport.rs`.
   - `get_write_buffer_size()` returns `0`
   - `get_write_buffer_limits()` returns `(0, 0)`
   - `set_write_buffer_limits()` is a no-op
+- several asyncio compatibility parameters are currently accepted only for API
+  shape and are not implemented:
+  - `create_connection(..., server_hostname=..., happy_eyeballs_delay=..., interleave=..., all_errors=...)`
+  - TLS timeout parameters such as `ssl_handshake_timeout` /
+    `ssl_shutdown_timeout`
+  - `shutdown_default_executor(timeout=...)`
 - subprocess support is intentionally incomplete:
   - `preexec_fn` is unsupported
   - text mode is rejected for higher-level
@@ -180,19 +206,6 @@ Build release wheels for CPython 3.8 through 3.14, plus the free-threaded
 scripts/build-wheels.sh
 ```
 
-## Publishing
-
-PyPI releases are published from Git tags that start with `v`, for example
-`v0.1.0`. The GitHub Actions workflow builds wheels by calling
-`scripts/build-wheels.sh`, builds an `sdist`, and then publishes the combined
-artifacts to PyPI with GitHub trusted publishing.
-
-Before the first release, configure the `rsloop` project on PyPI as a trusted
-publisher for this repository/workflow.
-
-Use a release build for benchmarks and runtime comparisons. A debug extension
-will make the Rust loop look much slower than it really is.
-
 ## Profiling
 
 Profiling support is behind the Cargo feature `profiler` and is disabled by
@@ -228,6 +241,7 @@ This writes an SVG flamegraph that you can open directly in a browser. Run the
 profile against a release build or the stack samples will be dominated by debug
 overhead. If the extension was built without `--features profiler`,
 `start_profiler()` and `profile()` will raise a runtime error.
+Only `format="flamegraph"` is currently implemented.
 
 ## Usage
 

{rsloop-0.1.1 → rsloop-0.1.2}/README.md

@@ -1,15 +1,34 @@
 <img src="./rsloop.png" alt="rsloop logo" align="center">
 
-# `rsloop`: An event loop for asyncio written in Rust
+# An event loop for asyncio written in Rust
 
-`rsloop` is a PyO3-based `asyncio` event loop. Each `rsloop.Loop` still owns a
-dedicated Rust runtime thread for timers, readiness polling, signal watchers,
-and transport coordination, but Python callbacks, tasks, and coroutines are
-driven on the thread that calls `run_forever()` / `run_until_complete()`
-(typically the main thread). The package exposes a Python module at
+[![PyPI - Version](https://img.shields.io/pypi/v/rsloop)](https://pypi.org/project/rsloop/)
+[![PyPI Downloads](https://static.pepy.tech/personalized-badge/rsloop?period=total&units=INTERNATIONAL_SYSTEM&left_color=BLACK&right_color=GREEN&left_text=downloads)](https://pepy.tech/projects/rsloop)
+
+`rsloop` is a PyO3-based `asyncio` event loop. Each `rsloop.Loop` owns a
+dedicated Rust runtime thread that handles loop coordination and I/O-related
+runtime work, while Python callbacks, tasks, and coroutines are executed on
+the thread that calls `run_forever()` / `run_until_complete()` (typically the
+main thread). The package exposes a Python module at
 `rsloop._loop` plus a small Python wrapper in `python/rsloop/__init__.py`.
 
-The project metadata currently targets Python `>=3.8`.
+The project metadata currently targets Python `>=3.8`. The current
+implementation is Unix-focused and intended for Linux and macOS; Windows is
+not supported by this codebase.
+
+## Install
+
+Install the published package from PyPI:
+
+```bash
+pip install rsloop
+```
+
+With `uv`:
+
+```bash
+uv add rsloop
+```
 
 ## Current Surface Area
 
@@ -61,7 +80,8 @@ Today’s codebase provides:
   - `create_unix_connection`
   - `connect_accepted_socket`
   - returned `Server` and `StreamTransport` objects
-  - `transport.close()` / `transport.abort()` fully close socket transports
+  - `transport.close()` / `transport.abort()` are implemented for socket
+    transports
 - pipe transports:
   - `connect_read_pipe`
   - `connect_write_pipe`
@@ -113,6 +133,12 @@ level transport implementation lives in `src/stream_transport.rs`.
   - `get_write_buffer_size()` returns `0`
   - `get_write_buffer_limits()` returns `(0, 0)`
   - `set_write_buffer_limits()` is a no-op
+- several asyncio compatibility parameters are currently accepted only for API
+  shape and are not implemented:
+  - `create_connection(..., server_hostname=..., happy_eyeballs_delay=..., interleave=..., all_errors=...)`
+  - TLS timeout parameters such as `ssl_handshake_timeout` /
+    `ssl_shutdown_timeout`
+  - `shutdown_default_executor(timeout=...)`
 - subprocess support is intentionally incomplete:
   - `preexec_fn` is unsupported
   - text mode is rejected for higher-level
@@ -148,19 +174,6 @@ Build release wheels for CPython 3.8 through 3.14, plus the free-threaded
 scripts/build-wheels.sh
 ```
 
-## Publishing
-
-PyPI releases are published from Git tags that start with `v`, for example
-`v0.1.0`. The GitHub Actions workflow builds wheels by calling
-`scripts/build-wheels.sh`, builds an `sdist`, and then publishes the combined
-artifacts to PyPI with GitHub trusted publishing.
-
-Before the first release, configure the `rsloop` project on PyPI as a trusted
-publisher for this repository/workflow.
-
-Use a release build for benchmarks and runtime comparisons. A debug extension
-will make the Rust loop look much slower than it really is.
-
 ## Profiling
 
 Profiling support is behind the Cargo feature `profiler` and is disabled by
@@ -196,6 +209,7 @@ This writes an SVG flamegraph that you can open directly in a browser. Run the
 profile against a release build or the stack samples will be dominated by debug
 overhead. If the extension was built without `--features profiler`,
 `start_profiler()` and `profile()` will raise a runtime error.
+Only `format="flamegraph"` is currently implemented.
 
 ## Usage
 

{rsloop-0.1.1 → rsloop-0.1.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "maturin"
 
 [project]
 name = "rsloop"
-version = "0.1.1"
+version = "0.1.2"
 description = "An event loop for asyncio written in Rust"
 readme = "README.md"
 license = { file = "LICENSE" }

{rsloop-0.1.1 → rsloop-0.1.2}/scripts/build-wheels.sh

@@ -10,10 +10,11 @@ usage() {
 Build release wheels for rsloop with uv-managed Python interpreters.
 
 Usage:
-  scripts/build-wheels.sh [--out DIR] [--skip-python-install] [-- maturin args...]
+  scripts/build-wheels.sh [--out DIR] [--target TRIPLE] [--skip-python-install] [-- maturin args...]
 
 Options:
   -o, --out DIR           Output directory for built wheels (default: dist/wheels)
+  -t, --target TRIPLE     Rust compilation target to pass to maturin
       --skip-python-install
                           Reuse installed interpreters instead of running `uv python install`
   -h, --help              Show this help
@@ -21,10 +22,12 @@ Options:
 Environment:
   RSLOOP_PYTHON_VERSIONS  Space-separated version list to override the defaults
                           (default: 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.14t)
+  RSLOOP_RUST_TARGET      Rust compilation target to pass to maturin
 
 Examples:
   scripts/build-wheels.sh
   scripts/build-wheels.sh --out wheelhouse
+  scripts/build-wheels.sh --target aarch64-apple-darwin
   RSLOOP_PYTHON_VERSIONS="3.12 3.13 3.14t" scripts/build-wheels.sh -- --features profiler
 EOF
 }
@@ -40,6 +43,7 @@ resolve_path() {
 
 OUTPUT_DIR="$DEFAULT_OUTPUT_DIR"
 INSTALL_PYTHONS=1
+RUST_TARGET="${RSLOOP_RUST_TARGET:-}"
 MATURIN_ARGS=()
 
 while (($#)); do
@@ -52,6 +56,14 @@ while (($#)); do
       OUTPUT_DIR="$2"
       shift 2
       ;;
+    -t|--target)
+      if (($# < 2)); then
+        echo "missing value for $1" >&2
+        exit 1
+      fi
+      RUST_TARGET="$2"
+      shift 2
+      ;;
     --skip-python-install)
       INSTALL_PYTHONS=0
       shift
@@ -102,6 +114,11 @@ for version in "${PYTHON_VERSIONS[@]}"; do
     --interpreter "$interpreter"
     --out "$OUTPUT_DIR"
   )
+  if [[ -n "$RUST_TARGET" ]]; then
+    maturin_cmd+=(
+      --target "$RUST_TARGET"
+    )
+  fi
   if ((${#MATURIN_ARGS[@]})); then
     maturin_cmd+=("${MATURIN_ARGS[@]}")
   fi

{rsloop-0.1.1 → rsloop-0.1.2}/uv.lock

@@ -4,5 +4,5 @@ requires-python = ">=3.8"
 
 [[package]]
 name = "rsloop"
-version = "0.1.1"
+version = "0.1.2"
 source = { editable = "." }