Pyjo-Reactor-Winloop
Low level event reactor with Winloop support for Pyjoyment.
Pyjo.Reactor.Winloop is Pyjo.Reactor.Asyncio with an event loop of its
own of Winloop, the fork of uvloop for Windows, so that the servers of
Pyjoyment, daemon and prethread, and the blocking requests of its user
agent run on Winloop, with coroutines, tasks and the libraries of asyncio
along with them.
Installation
From PyPI, with Pyjoyment and Winloop, which it depends on, on Windows, with CPython:
pip install Pyjo-Reactor-Winloop
or, in a project managed with uv:
uv add Pyjo-Reactor-Winloop
The development version is installed from the Git repository:
pip install git+https://github.com/pyjoyment/Pyjo-Reactor-Winloop
Usage
Select the reactor with PYJO_REACTOR before Pyjo.IOLoop is loaded, in
PowerShell:
$env:PYJO_REACTOR = 'Pyjo.Reactor.Winloop'
python myapp.py daemon
python myapp.py prethread
or in Git Bash:
PYJO_REACTOR=Pyjo.Reactor.Winloop python myapp.py daemon
Examples
examples/hello_world_winloop.py runs Pyjo.HelloWorld on the server of
Pyjoyment on Winloop until Ctrl-C or Ctrl-Break, in a with block, which
closes the listen sockets of the server at its end:
import os
# The reactor of Pyjoyment on Winloop, selected before Pyjo.IOLoop is loaded
os.environ['PYJO_REACTOR'] = 'Pyjo.Reactor.Winloop'
import Pyjo.HelloWorld # noqa: E402
import Pyjo.Server.Daemon # noqa: E402
# The server of Pyjoyment on Winloop, until Ctrl-C or Ctrl-Break, which closes its listen sockets at the end of the block
with Pyjo.Server.Daemon.new(app=Pyjo.HelloWorld.new(), listen=['http://*:3000']) as daemon:
daemon.run()
$ python examples/hello_world_winloop.py
Web application available at http://127.0.0.1:3000
$ curl http://127.0.0.1:3000/
Your Pyjo is working!
examples/asyncio_winloop.py is a coroutine on the loop of Winloop, which
requests the server of Pyjoyment in the same loop with the streams of asyncio
and with the user agent of Pyjoyment, as the libraries of asyncio run along
with the reactor:
import os
# The reactor of Pyjoyment on Winloop, selected before Pyjo.IOLoop is loaded
os.environ['PYJO_REACTOR'] = 'Pyjo.Reactor.Winloop'
import Pyjo.HelloWorld # noqa: E402
import Pyjo.IOLoop # noqa: E402
import Pyjo.Server.Daemon # noqa: E402
import Pyjo.UserAgent # noqa: E402
import asyncio # noqa: E402
import winloop # noqa: E402
# A coroutine on the loop of Winloop, with the streams of asyncio and the user agent of Pyjoyment, both requesting the
# server of Pyjoyment in the same loop
async def main(port):
reader, writer = await asyncio.open_connection('127.0.0.1', port)
writer.write(b'GET / HTTP/1.1\r\nHost: 127.0.0.1\r\nConnection: close\r\n\r\n')
print(f'asyncio: {(await reader.readline()).decode().strip()}')
writer.close()
await writer.wait_closed()
with Pyjo.UserAgent.new() as ua:
tx = await ua.get_p(f'http://127.0.0.1:{port}/')
print(f'Pyjo.UserAgent: {tx.res.code} {tx.res.text}')
return 'winloop' if isinstance(asyncio.get_running_loop(), winloop.Loop) else 'asyncio'
# The server, on a port that the system picks, which closes its listen sockets at the end of the block
with Pyjo.Server.Daemon.new(app=Pyjo.HelloWorld.new(), listen=['http://127.0.0.1'], silent=True) as daemon:
port = daemon.start().ports()[0]
Pyjo.IOLoop.singleton.reactor.run_coroutine(
main(port),
lambda loop: (print(f'loop: {loop}'), Pyjo.IOLoop.stop()),
lambda err: (print(f'error: {err}'), Pyjo.IOLoop.stop()),
)
Pyjo.IOLoop.start()
$ python examples/asyncio_winloop.py
asyncio: HTTP/1.1 200 OK
Pyjo.UserAgent: 200 Your Pyjo is working!
loop: winloop
examples/loopback_winloop.py is a server of Pyjoyment and its user agent on
the loop of Winloop, a blocking request, which runs the event loop until the
response, and the class of the reactor and whether its loop is one of
Winloop, which Build checks with the wheel:
import os
# The reactor of Pyjoyment on Winloop, selected before Pyjo.IOLoop is loaded
os.environ['PYJO_REACTOR'] = 'Pyjo.Reactor.Winloop'
import Pyjo.HelloWorld # noqa: E402
import Pyjo.IOLoop # noqa: E402
import Pyjo.Server.Daemon # noqa: E402
import Pyjo.UserAgent # noqa: E402
import winloop # noqa: E402
# The server, on a port that the system picks, and the user agent, in the same event loop, which close their sockets at
# the end of the block
with (
Pyjo.Server.Daemon.new(app=Pyjo.HelloWorld.new(), listen=['http://127.0.0.1'], silent=True) as daemon,
Pyjo.UserAgent.new(ioloop=Pyjo.IOLoop.singleton) as ua,
):
# A blocking request, which runs the event loop of the server on Winloop until the response
tx = ua.get(f'http://127.0.0.1:{daemon.start().ports()[0]}/')
reactor = Pyjo.IOLoop.singleton.reactor
print(type(reactor).__name__, 'winloop' if isinstance(reactor.loop, winloop.Loop) else 'asyncio')
print(tx.result.code, tx.result.text)
$ python examples/loopback_winloop.py
Pyjo_Reactor_Winloop winloop
200 Your Pyjo is working!
Documentation
The API of the module and the examples are on Read the Docs.
Status
A reactor of Pyjoyment in a distribution of its own, as Pyjo-Reactor-Uvloop, which it follows on Windows.
Metadata
Release files for Pyjo-Reactor-Winloop 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyjo_reactor_winloop-0.1.0.tar.gz | 22.6 kB | With provenance | Details for pyjo_reactor_winloop-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyjo_reactor_winloop-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for pyjo_reactor_winloop-0.1.0-py3-none-any.whl |
Total release size: 34.7 kB
Release files / pyjo_reactor_winloop-0.1.0.tar.gz
| Download URL | pyjo_reactor_winloop-0.1.0.tar.gz |
|---|---|
| Size | 22.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
152eb70c8b010ece0038b021225e2cbc6035d5b3108eb1126ef71509578068d1
|
|
BLAKE2b-256 checksum How to use checksums |
b444f14eecce239f88a03484392854b17ccb1acf055c90ce1d127f3fc58781b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logRelease files / pyjo_reactor_winloop-0.1.0-py3-none-any.whl
| Download URL | pyjo_reactor_winloop-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2bc6586a764913836796a669e5c61d6a59d8345087fb7e0cd3f7bc0b41579fb0
|
|
BLAKE2b-256 checksum How to use checksums |
121edcf464c53a1da6e98c71f9c61f8ed47f135d489f7a4186da228cd0058a54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logSecurity for Pyjo-Reactor-Winloop 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pyjo_reactor_winloop-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.