Polyphony
trio
Polyphony | trio | |
---|---|---|
22 | 19 | |
651 | 5,895 | |
0.0% | 1.1% | |
8.3 | 9.5 | |
about 1 month ago | 6 days ago | |
C | Python | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Polyphony
-
Should You Be Scared of Unix Signals?
When using green threads/fibers/coroutines, an interesting technique to make signal handling safer is to run the signal handler asynchronously on a separate fiber/green thread. That way most of the problems of dealing with signals go away, and there's basically no limitation on what you can do inside the signal handler.
I've successfully used this technique in Polyphony [1], a fiber-based Ruby gem for writing concurrent programs. When a signal occurs, Polyphony creates a special-purpose fiber that runs the signal handling code. The fiber is put at the head of the run queue, and is resumed once the currently executed fiber yields control.
[1] https://github.com/digital-fabric/polyphony
-
Polyphony 1.4 Released
Read the release notes here: https://github.com/orgs/digital-fabric/discussions/110 The Polyphony docs: https://www.rubydoc.info/gems/polyphony The Polyphony repository: https://github.com/digital-fabric/polyphony
- Polyphony: Fine-Grained Concurrency for Ruby
-
Polyphony 0.99 released. Last release before 1.0!
Polyphony is a gem for building highly-concurrent Ruby programs. It utilizes Ruby fibers to provide a high-performance safe environment for launching any number of concurrent operations. Under the hood, Polyphony employs io_uring to maximize I/O performance (libev is used on platforms other than recent Linux kernels).
- Polyphony – Fine-grained concurrency for Ruby
-
About that monkey-patching business...
Is monkey-patching inherently bad? Should its use make Polyphony illegitimate? These are the questions I'm exploring in my latest article.
-
Async Ruby
how is this diff from: https://github.com/digital-fabric/polyphony
-
Embracing Infinite Loops with Ruby and Polyphony
Infinite loops are great for expressing long-running concurrent operations. In this article I’ll discuss the use of infinite loops as a major construct when writing concurrent apps in Ruby using Polyphony. I’ll show how infinite loops differ from normal, finite ones; how they can be used to express long-running tasks in a concurrent environment; and how they can be stopped. Read it now!
-
What's new in Polyphony and Tipi - August 2021 edition
Polyphony is a library for writing highly concurrent Ruby apps. Polyphony harnesses Ruby fibers and a powerful io_uring-based I/O runtime to provide a solid foundation for building high-performance concurrent Ruby apps.
-
Sorbet Compiler: An experimental, ahead-of-time compiler for Ruby
> Curious if there’s anything public about improving ruby performance from the I/O angle mentioned in the post.
I'm currently working on Polyphony [0], a Ruby gem for writing highly-concurrent Ruby apps. It uses Ruby fibers under the hood, and does I/O using io_uring (on Linux, there is also a libev-based backend).
[0] https://github.com/digital-fabric/polyphony
trio
-
trio VS awaits - a user suggested alternative
2 projects | 9 Dec 2023
-
In what ways are channels are better than the traditional await?
Incidentally, the alternative event loop implementation trio in python does not have "gather", you also need channels, and it's a deliberate design choice - there is some discussion about that in this ticket https://github.com/python-trio/trio/issues/2188
- Polyphony: Fine-Grained Concurrency for Ruby
-
This Week In Python
trio – a friendly Python library for async concurrency and I/O
-
Python projects with best practices on Github?
trio. the best code, the best documentation, awesome community.
- Trio: Structured Concurrency for Python
-
The Heisenbug lurking in your async code (Python)
I'll +1 the Trio shoutout [1], but it's worth emphasizing that the core concept of Trio (nurseries) now exists in the stdlib in the form of task groups [2]. The article mentions this very briefly, but it's easy to miss, and I wouldn't describe it as a solution to this bug, anyways. Rather, it's more of a different way of writing multitasking code, which happens to make this class of bug impossible.
[1] https://github.com/python-trio/trio
[2] https://docs.python.org/3/library/asyncio-task.html#task-gro...
-
The gotcha of unhandled promise rejections
It's similar to manual memory management.
Structured concurrency is one approach to solving this problem. In a structured concurrency a promise would not go out of scope unhandled. Not sure how you would add APIs for it though.
See Python's trio nurseries idea which uses a python context manager.
https://github.com/python-trio/trio
I'm working on a syntax for state machines and it could be used as a DSL for promises. It looks similar to a bash pipeline but it matches predicates similar to prolog.
In theory you could wire up a tree of structured concurrency with this DSL.
https://github.com/samsquire/ideas4#558-assign-location-mult...
-
Python Asyncio: The Complete Guide
Not complete - doesn't include Task Groups [1]
In fairness they were only included in asyncio as of Python 3.11, which was released a couple of weeks ago.
These were an idea originally from Trio [2] where they're called "nurseries" instead of "task groups". My view is that you're better off using Trio, or at least anyio [3] which gives a Trio-like interface to asyncio. One particularly nice thing about Trio (and anyio) is that there's no way to spawn background tasks except to use task groups i.e. there's no analogue of asyncio's create_task() function. That is good because it guarantees that no task is ever left accidentally running in the background and no exception left silently uncaught.
[1] https://docs.python.org/3/library/asyncio-task.html#task-gro...
[2] https://github.com/python-trio/trio
[3] https://anyio.readthedocs.io/en/latest/
- Anyone here able to help with a python issue?
What are some alternatives?
Async Ruby - An awesome asynchronous event-driven reactor for Ruby.
uvloop - Ultra fast asyncio event loop.
Concurrent Ruby - Modern concurrency tools including agents, futures, promises, thread pools, supervisors, and more. Inspired by Erlang, Clojure, Scala, Go, Java, JavaScript, and classic concurrency patterns.
curio - Good Curio!
EventMachine - EventMachine: fast, simple event-processing library for Ruby programs
asyncio
Celluloid - Actor-based concurrent object framework for Ruby
Twisted - Event-driven networking engine written in Python.
render_async - render_async lets you include pages asynchronously with AJAX
LDAP3 - a strictly RFC 4510 conforming LDAP V3 pure Python client. The same codebase works with Python 2. Python 3, PyPy and PyPy3
Opal-Async - Non-blocking tasks and enumerators for Opal.
DearPyGui - Dear PyGui: A fast and powerful Graphical User Interface Toolkit for Python with minimal dependencies