MOMortyWaves·Jan 31, 2025
In Show HN: Reactive Signals for Python – inspired by Angular's reactivity modelReactiveX
RxPY
Python2014–2025
ReactiveX / RxPY
RxPY
ReactiveX for Python
10Distinct people
10Mentions
0Explicit recommenders
5KGitHub stars
What to know before exploring
What it is
ReactiveX for Python
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year10 dated mentions
Observed mentions: 2014-11-07 15:41:51 UTC to 2025-01-31 07:14:27 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
10 sourcesCool (probably), but it's not clear what it does or how useful it is when one doesn't know anything about Angular signals. Could you explain?
Also, care to compare to RxPY? (https://github.com/ReactiveX/RxPY)
In Show HN: Reactive Signals for Python – inspired by Angular's reactivity modelShouldn't be too hard. For example you could use: https://github.com/ReactiveX/RxPY.
Then your central state is assigned to a Subject and all widgets have an reference to an observer. As soon as the central state value changes, the callback in the observer is triggered and you can fire the update method for the widget using the central state value.
In Guietta – Python module to create simple GUIsA lot of the newer stuff in JS is great. The baggage is what bothers me. For all the flak Java gets for having ancient stuff, the old stuff in JS is way worse.
Java cruft is better these days if you use 11+ with Lombok. Almost decent. You can also use Kotlin which is honestly good, but unless you pay up for IntelliJ support for it is mediocre at best. I really like Typescript's nominal typing, wish Java chose that road.
I'm not a Python guy, but Java has Streams and RxJava which is great for functional stuff. I'm pretty sure RxJS was originally a JS port of RxJava. The same library has flavors in most languages now, you may be interested in the Python version https://github.com/ReactiveX/RxPY
Publishing to NPM registry is much easier, but everything else is worse. I blame much of it on the lacking standard library. But JS not packaging li
Read the rest
braries in archives, plus using minifaction instead of a bytecode format both suck. JS has a huge parsing problem, for some sites half the page load time is parsing JS. VM's with an efficient code representation like C# and Java avoid this. Java and C# package source, compiled code, and documentation in a standardized (and efficient) way. NPM just isn't there yet.
Java is missing async await, but there's also grumbles about supporting it and function coloring. Java has Akka, promises (CompletableFuture), parallel streaming, and traditional threads. The problem with supporting async/await without threads is that it doesn't solve for modern CPU's having more and more cores. In Java/C# its trivial to use the whole machine and share structures.
You should try Vert.X, its very similar to Express. I would almost dare say Express borrowed a lot from it.
There's some good design decisions rolling in, but still plenty of reasons I avoid it when I can.
> which has a python implementation
I think this is the most popular one:
https://github.com/ReactiveX/RxPY
This one is a rewrite of RxPY, that makes use of async / await / asyncio:
https://github.com/dbrattli/aioreactive
Pretty interesting stuff!
In Databot: High-performance Python data-driven programming frameworkReactive Extensions for Python (RxPY)
1 points · Open discussionThis is quite cool, though it seems similar to RxPy (https://github.com/ReactiveX/RxPY)
In Show HN: Python library for functional programmingI "learned" RxPy in a couple hours yesterday (a 3rd party lib I'm using has an interface that requires me to use them), and I figure I'll share a bit about my experience:
1) the documentation is supremely lacking (subjects aren't even mentioned in the RxPy repo https://github.com/ReactiveX/RxPY)
2) the generic documentation points to language specific documentation – that's 80% just "TBD" (http://reactivex.io/documentation/subject.html)
3) it's actually quite simple once you figure out it's just code level pub/sub with a new naming convention.
4) there seem to be some opinionated perspectives around using it in the community, though largely from a JS perspective (look into "should I use subjects").
Despite those flaws, I've found it pretty accessible, and I'll actually switch out some home-grown code for it.
[edit] I noticed some other co
Read the rest
mments complaining about execution handling (threads, etc.) so I figured I'd update this and say, maybe I got lucky as it's all pretty straightforward in Python (as long as you understand your app's execution environment (threads, asyncio, etc.) -> https://github.com/ReactiveX/RxPY#schedulers
Qt has been indispensable to my daily work. When I first started my current job, I had to convince my boss that we should transition from C# to PyQt (and also the rest of the Python ecosystem, which is awesome because we do commercial scientific computing). Mixing Python and Qt has been great for productivity, as you can imagine. There is also a great Python visualization ecosystem based on PyQt/PySide including pyqtgraph and vispy. Lastly, the documentation is absolutely outstanding, and the community is very active.
A project I have been wanting to start is to use Qt as a substrate for a (functional) reactive programming framework in Haskell or Python. The Haskell lib could be based on any current FRP implementation, and the Python lib could be based on RxPY [1].
One thing I would change in Qt would be the Model/View system. I try to us
Read the rest
e a strict Model-View-Presenter approach, but since we have millions of rows in our tables we have to use Qt's Models/Views instead of controlling all view behavior ourselves. It would be nice to have performant views easily while using a different API, instead of being forced to use the QAbstractItemModel API.
Congrats Qt project, and thanks for the hard work!
[1] https://github.com/ReactiveX/RxPY
Reactive Extensions for Python
1 points · Open discussion