Skip to main content

Asyncio event loop based on tokio-rs (WIP) Build Status Join the dev chat at https://gitter.im/PyO3/Lobby

async-tokio is a drop-in replacement of the built-in asyncio event loop. async-tokio is implemented in rust and uses tokio-rs under the hood and PyO3 python binding.

Using tokio loop

You can create an instance of the loop manually, using:

import tokio

policy = tokio.EventLoopPolicy()
asyncio.set_event_loop_policy(policy)

Development of tokio loop

To build tokio loop, you’ll need rust nightly and Python 3.6. The best way is to create a virtual env, so that you’ll have python commands pointing to the correct tools.

  1. git clone git@github.com:PyO3/tokio.git

  2. cd tokio

  3. make build

  4. make test

Status

At the moment async-tokio works on unix like systems only. Supported api:

  • time api (call_at, call_later)

  • sockets api (sock_xxx methods)

  • tcp (client/server)

  • unix domain socket

  • dns

  • pipes

  • subprocess

  • signals

  • executors

UDP support is missing.

License

async-tokio is offered under the Apache 2.0 licenses.

CHANGES

0.2.0 (07-23-2017)

  • Use pyo3 python binding PyO3 python binding.

  • Implement more asyncio APIs

0.1.0

Initial release

Metadata

Release files for tokio 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tokio 0.2.0
File Size Uploaded Provenance Actions
tokio-0.2.0.tar.gz 102.3 kB Without provenance Details for tokio-0.2.0.tar.gz

Release files / tokio-0.2.0.tar.gz

Download URL tokio-0.2.0.tar.gz
Size 102.3 kB
Tags Source
SHA-256 checksum
How to use checksums
94bf11cbcfaefa1d5f90232fd8f1dd9a26aca64de41845c0d9d058a5fea92f50
BLAKE2b-256 checksum
How to use checksums
38797039fb417ab95d511bca9389cb459c1298e3227389a1fc27a417ab9791a8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for tokio 0.2.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Release history Release notifications | RSS feed

This release

0.2.0 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page