dunsync 0.1.1

Identical to unsync, but supports cpu-bound continuation functions

dunsync

Identical to unsync, except that continuation callbacks receives the result of the Unfuture rather than the Unfuture itself. This allows cpu-bound @unsync functions to be chained together with other regular functions and IO-bound @unsync functions, as long as the result is pickleble.

Example

from dunsync import unsync
import asyncio
import time

@unsync()  # Will run in an asyncio event loop
async def download_data(url):
    await asyncio.sleep(1)
    return 'data'

@unsync(cpu_bound=True)  # Will run in a separate process
def process_data(data):
    time.sleep(1)
    return 'processed data'

@unsync()  # Will run in a separate thread
def store_processed_data(data):
    time.sleep(1)
    return 'Done'

tasks = [
    download_data(url).then(process_data).then(store_processed_data)
    for url in ['url1', 'url2', 'url3']
]

for task in tasks:
    print(task.result())

Replacing dunsync with unsync in the above example results in the error TypeError: cannot pickle '_asyncio.Task' object, since the Unfuture wraps other objects (either asyncio.Task, as in this example, or threading.Thread) which cannot be pickled in order to be passed to a separate process.

Installation

Using pip:

pip install dunsync

Using pipenv:

pipenv install dunsync

Using poetry:

poetry add dunsync