universalasync
A library to help automate the creation of universal python libraries
Overview
Have you ever been frustrated that you need to maintain both sync and async versions of your library, even thought their code differs by just async and await? You might have came up to rewriting your code before release or other unreliable solutions.
This library helps you to focus only on the main async implementation of your library: sync one will be created automatically
Via decorating all your public methods, the wrapped functions automatically detect different conditions and run the functions accordingly.
If user uses your library in async context, minimal overhead is added, it just returns the coroutine right away.
Otherwise the library calls the coroutine via various loop methods, like as if you did it manually.
There should be no issues at all, the only limitation is that signals and async subprocesses are supported only when running in the main thread.
Also note that when run from a different os thread, the library will create a new event loop there and run coroutines.
This means that resources bound to a certain event loop (like aiohttp.ClientSession) need one instance per event loop.
LoopLocal keeps one value per event loop, and closes each of them on the loop that owns it: when you call close(), or when it is garbage collected.
import aiohttp
from universalasync import LoopLocal, wrap
@wrap
class Client:
def __init__(self):
self._sessions = LoopLocal(aiohttp.ClientSession.close)
async def help(self):
async with self._sessions.get(aiohttp.ClientSession).get("https://example.com") as response:
return await response.text()
def close(self): # await it in async code
return self._sessions.close()
For API reference see the docs
Installation
pip install universalasync
Example of usage
import asyncio
import threading
from universalasync import async_to_sync_wraps, wrap
# wrap needed methods one by one
class Client:
@async_to_sync_wraps
async def help(self): ...
@async_to_sync_wraps
@property
async def async_property(self): ...
# or wrap whole classes
@wrap
class Client:
async def help(self): ...
@property
async def async_property(self): ...
client = Client()
def sync_call():
client.help()
client.async_property
async def async_call():
await client.help()
await client.async_property
# works in all cases
sync_call()
asyncio.run(async_call())
threading.Thread(target=sync_call).start()
threading.Thread(target=asyncio.run, args=(async_call(),)).start()
The mode is chosen when a wrapped method is called: outside a running event loop it runs to completion and returns the result.
So asyncio.run(client.help()) doesn't work, as client.help() has already run before asyncio.run starts a loop. Await it inside a coroutine instead, like async_call above.
Copyright and License
Copyright (C) 2021 MrNaif2018
Universal async-sync wrapper initially based on this implementation
Licensed under the MIT license
Metadata
Release files for universalasync 0.6.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 |
|---|---|---|---|---|
| universalasync-0.6.1.0.tar.gz | 11.8 kB | With provenance | Details for universalasync-0.6.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| universalasync-0.6.1.0-py3-none-any.whl | Python 3 | none | any | Details for universalasync-0.6.1.0-py3-none-any.whl |
Total release size: 20.3 kB
Release files / universalasync-0.6.1.0.tar.gz
| Download URL | universalasync-0.6.1.0.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dbe075a10123c3d137a9ef46f1c07fadb77204b3d4dc356d8b59e7cf7e9380d
|
|
BLAKE2b-256 checksum How to use checksums |
e2c11f3a0eab95d77442b013c958bded39d3a8a02b17e7892c957c48d8236f79
|
| 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 Oct 31, 2026.
Transparency logRelease files / universalasync-0.6.1.0-py3-none-any.whl
| Download URL | universalasync-0.6.1.0-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f59456965905e5fedfd0ccdc4b0429678995d8e7e2ad0e8168599001d536297
|
|
BLAKE2b-256 checksum How to use checksums |
b378fcd80a417ea9c1441ae4f92b3d39939c996cbc1e66b9374693872351b187
|
| 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 Oct 31, 2026.
Transparency logSecurity for universalasync 0.6.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for universalasync-0.6.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 Oct 31, 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.