| Name : python311-unsync
| |
| Version : 1.4.0
| Vendor : openSUSE
|
| Release : 1.1
| Date : 2025-01-16 13:36:55
|
| Group : Unspecified
| Source RPM : python-unsync-1.4.0-1.1.src.rpm
|
| Size : 0.03 MB
| |
| Packager : https://bugs_opensuse_org
| |
| Summary : Unsynchronize asyncio
|
Description :
Unsynchronize `asyncio` by using an ambient event loop in a separate thread.
1. Mark all async functions with `AATTunsync`. May also mark regular
functions to execute in a separate thread.
* All `AATTunsync` functions, async or not, return an `Unfuture`
2. All `Futures` must be `Unfutures` which includes the result of an
`AATTunsync` function call, or wrapping `Unfuture(asyncio.Future)` or
`Unfuture(concurrent.Future)`. `Unfuture` combines the behavior of
`asyncio.Future` and `concurrent.Future`:
* `Unfuture.set_value` is threadsafe unlike `asyncio.Future`
* `Unfuture` instances can be awaited, even if made from
`concurrent.Future`
* `Unfuture.result()` is a blocking operation *except* in
`unsync.loop`/`unsync.thread` where it behaves like
`asyncio.Future.result` and will throw an exception if the future
is not done
3. Functions will execute in different contexts:
* `AATTunsync` async functions will execute in an event loop in
`unsync.thread`
* `AATTunsync` regular functions will execute in
`unsync.thread_executor`, a `ThreadPoolExecutor`
* `AATTunsync(cpu_bound=True)` regular functions will execute in
`unsync.process_executor`, a `ProcessPoolExecutor`
|
RPM found in directory: /vol/rzm3/linux-opensuse/tumbleweed/repo/oss/noarch |
Hmm ... It's impossible ;-) This RPM doesn't exist on any FTP server
Provides :
python3-unsync
python3.11dist(unsync)
python311-unsync
python3dist(unsync)
Requires :
