History
Why one more async library? Broomio started as an experiment. This code meant to be thrown away. I was inspired by curio and trio libraries, code looked so clean and easy to understand. That was brave new Python, no callbacks, low maintenance. Curio is the first challenger, questioning existing standard library choices; and Trio is the place where real science happens. Also authors of both libraries are really friendly, thank you David Beazley and Nathaniel J. Smith! However, I was curios what are Python asyncio limits? Can asyncio based network server written in beautiful clean manner be as performant as raw epoll based with ugly spagetti callbacks? It turns out the answer is yes, but not without some tradeoffs.
Getting Started
Installation
Broomio can be installed with pip.
pip3 install broomio
Usage
First of all, you’ll need a loop. Loops are common concept in async libraries. Broomio provides no default loop, so loop should be created and started explicitly.
from broomio import Loop loop = Loop() loop.run()
However this loop has nothing to do and will exit immediately. Lets add some coroutine and execute it a few times. Read more about coroutines in PEP 0492.
from broomio import Loop
from broomio import sleep
from time import time
async def test(index):
print(f'{index} started at {time()}')
await sleep(2)
print(f'{index} stopped at {time()}')
loop = Loop()
loop.start_soon(test(1))
loop.start_soon(test(2))
loop.start_soon(test(3))
loop.run()
You will see output like the following
3 started at 1456789015.0144565 2 started at 1456789015.0147984 1 started at 1456789015.0149508 3 stopped at 1456789017.0166693 2 stopped at 1456789017.0171447 1 stopped at 1456789017.0180902
The first thing to notice is that some functions which pause or block execution, like sleep, should be called with await. Skipping await will lead to all kinds of unexpected bad consequences. So be careful. The second thing to notice is that coroutines behave more or less like threads. Please, find bellow equivalent code with threads.
from threading import Thread
from time import sleep
from time import time
def test(index):
print(f'{index} started at {time()}')
sleep(2)
print(f'{index} stopped at {time()}')
t1 = Thread(target=lambda: child(1))
t2 = Thread(target=lambda: child(2))
t3 = Thread(target=lambda: child(3))
t1.start()
t2.start()
t3.start()
t1.join()
t2.join()
t3.join()
Output will be similar
1 started at 1456789015.0149508 3 started at 1456789015.0144565 2 started at 1456789015.0147984 1 stopped at 1456789017.0180902 2 stopped at 1456789017.0171447 3 stopped at 1456789017.0166693
Difference is that coroutines actually work in context of single thread. There are no operating system level threads or anything similar, it’s pure user code solution. Kernel is not aware of coroutines.
Find more examples in corresponding folder in source code.
Metadata
Release files for broomio 0.5.190510
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| broomio-0.5.190510-py3-none-any.whl | Python 3 | none | any | Details for broomio-0.5.190510-py3-none-any.whl |
Release files / broomio-0.5.190510-py3-none-any.whl
| Download URL | broomio-0.5.190510-py3-none-any.whl |
|---|---|
| Size | 23.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00c3ca04aa1d8fcf2fc9969f844341af212c230b44279558a2c554f5234dec08
|
|
BLAKE2b-256 checksum How to use checksums |
d780fd6220913fac895211488f60e03839bcdc2d2ba47dc4131757bd14b70d44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.7.3
|
Security for broomio 0.5.190510
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.