The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...

The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.

RPM resource python311-unsync

Unsynchronize `asyncio` by using an ambient event loop in a separate thread. 1. Mark all async functions with `@unsync`. May also mark regular functions to execute in a separate thread. * All `@unsync` functions, async or not, return an `Unfuture` 2. All `Futures` must be `Unfutures` which includes the result of an `@unsync` 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: * `@unsync` async functions will execute in an event loop in `unsync.thread` * `@unsync` regular functions will execute in `unsync.thread_executor`, a `ThreadPoolExecutor` * `@unsync(cpu_bound=True)` regular functions will execute in `unsync.process_executor`, a `ProcessPoolExecutor`

Found 1 sites for python311-unsync

• https://github.com/alex-sherman/unsync

Found 3 RPM for python311-unsync

Generated by rpm2html 1.6

Fabrice Bellet