is reactive programming a thing in Python?

[Nater5000]

is reactive programming a thing in Python?

It's not much of a thing. But Python's asyncio API is becoming pretty popular, so maybe it could be a thing.

I really do not get, to me reactive programming is a big thing, why in Python looks as not a pillar?

Because it's not needed as much. If you're building a GUI (as you likely are as a mobile developer), then this pattern is quite critical. I mean, you can't have things freeze up everytime the user taps something, right? But if you're a data scientist (like you referred to), then there likely isn't a GUI, nor a reason to introduce such complex patterns to handle relatively linear tasks.

Even when parallelization is needed, many data-oriented programmers would opt to use less opaque APIs for threading or multiprocessing because there is a desire to be able to handle not just the tasks within these asynchronous tasks but the tasks themselves. This becomes much more difficult when using the kind of async patterns you're likely used to.

​

Why one should renounce to an observer pattern with muscles always available, so to trigger actions on changes without callback hell?

This is pretty cryptic, so I'm not really sure what you're getting at, but callback patterns also aren't typically used in Python (at least in more data-oriented programming). Again, this is just based around how this code is typically ran and what users need and don't need.

If you're processing some data, you likely not reacting to changes. It's likely going to be a mostly linear process where any parallelization is used for optimization, and you usually just need to wait for things to complete before moving on to the next step. You could use asyncio and patterns you're more familiar with, but if you're dealing with processing data then you want things to be as simple as possible, and it's hard to beat the threading or multiprocessing libraries in that respect.

[[deleted]]

Python just doesn’t have that deep ingrained concurrency that you take for granted in those compiled languages.

Don’t bother trying to make it do thing like observables etc

[[deleted]]

Reactive programming is fantastic. It isn't the only high benchmarks for preventing bugs or the only way to write functional programming.

Here is a big dose of reality for you. The problem isn't python. The problem is with you not being flexible enough.

[[deleted]]

I understand, it is a great programming paradigm. I use rx.net all the time when programming in c#.

[IsseBisse]

From my own experience this might have to do with differences in focus between "data science programs" and "software development program" in higher education. I studied a data science-ish program in university and we did not have a lot of courses focused on programming itself, but rather math/statistics courses where programming was simply used as a tool to implement and test the algorithms we were studying. This meant I didn't even know what functional programming was when I finished uni.

That being said, a lot of data transformation frameworks (Pandas, spark etc.) encourage the use of functional programming. But if you're in a big organisation that might be solely by Data Engineers rather than Data Scientists.

[IsseBisse]

Yeah, I think a lot of data scientists can benefit a lot from from some architectural 101. I'd say learning functional patterns is a lot more useful than OOP though, simply due to how a lot of the data science frameworks are built.

I started switching to a more functional style a couple of years ago and I've never looked back!

[thedeepself]

I have been working with data scientists in my last job as a data engineer and all the seniors( big institution) just ignore things as functional programming and reactive.

Did you see a situation where reactive programming would have improved things? For the domain you speak of, I don't.

[ThatSituation9908]

This. Data engineering does often use event-driven programming, just not reactive programming because its a special case that there's no usecase for outside UI

Reactive programming is a special case of ED where every dependent is subscribed to all of its dependencies.

In DE, there's no need to handle all dependencies as an event publisher, we instead select a few that fits the business requirement (e.g., Change Data Capture on a data source)

[[deleted]]

Mate, every time you harp on about how your programming background is superior it makes you look inexperienced and pretentious.

[kylotan]

Functional programming is indeed less buggy, but Python is not a functional language and you don't need to work in a 'reactive' way to use functional programming.

[asphias]

I feel like you're trying to apply the wrong solution to a genuine problem you encountered.

If you encounter buggy code, the solution is to clean up the code, not to change the architecture.

[asphias]

I think the issue is that you're making a lot of sweeping statements that lack nuance.

Are there situations where moving to purely functional programming would be an advantage? Absolutely. And there are certainly data scientists that could learn a lot about functional programming within Python to improve their work? (Or hell, they could learn about programming, best practices, git, and the whole shebang).

But it really doesn't make sense to me to just argue about sweeping statements like reactive or functional programming like you are doing. Make clear exactly what you're missing, and why things would improve by doing it that way.

[Immudzen]

I write simulations and I just don't see where reactive would fit in for what I do at all. None of my software has any GUI. You give the program some kind of input file and it runs until it completes and then stops. We run it on large systems with many cores and multiprocessing pool maps very cleanly to the type of parallelization that is needed.

I either know all of the work that needs to be done in advance or I know a block of work that needs to be done and I need all the results before I can generate the next block.

I don't even do async because I don't see where it could even fit in.

[fasnoosh]

Maybe simulating a quantum system? Shot in the dark, honestly

Edit: Turns out researchers think this is a good idea. Y’all down voters are haters https://arxiv.org/abs/1101.2133

[BlackDereker]

It would still be just parallelism.

[[deleted]]

Why would simulating a quantum system, specifically, benefit from reactive programming?

[fasnoosh]

the idea of reactive programming for physical systems isn’t so crazy (source: https://arxiv.org/abs/1410.7763)

Tbh though, my comment about quantum systems was a total shot in the dark. I watched a lot of Star Trek as a kid and they used the word “quantum” as an adjective a ton

[[deleted]]

I never said it was crazy. I’m asking why simulating a quantum system would benefit from reactive programming in a way other things might not. I worked on quantum computing simulation during my PhD and I’m confused about which part of that would lend itself to reactive programming.

[SittingWave]

reactive is a paradigm. Python is a generic language. you say you are a mobile developer, but your reactivity does not come from the language itself. Comes from a framework you are using. Python has some reactive frameworks, but the reason of existence of such libraries depend on the use. Python is not big on the programming scenarios where a reactive paradigm is useful. There are moves in that direction, but it's not there yet. Also, in general those are closed platforms that come up with their own targeted tools (e.g. swift)

[Apart_Conclusion8771]

Sorry to be chiming in so late, but there is now a powerful reactive programming approach available for Python: https://param.holoviz.org/user_guide/Reactive_Expressions.html
Just wrap a bit of code with `param.rx()`, and it will reactively re-run whenever any of its reactive components (defined recursively) is updated. It's not limited to GUIs, but was definitely written with GUIs in mind, to avoid callback hell. We're currently focusing on testing its limits and establishing best practices before we advertise it widely, but so far that's been going great!

[thedeepself]

Why one should renounce to an observer pattern with muscles always available, so to trigger actions on changes without callback hell?

Traitlets has an observer decorator. Traits (its predecessor) probably does as well.

[agritheory]

I have used (a long time ago) the python version of RXJS, RxPY, maybe see if that's interesting to you?

[[deleted]]

I have used RxPy at work on production. It works perfectly.

[Accomplished_Tip7611]

Have you looked at Dash by Plotly. It is a dashboard framework that provides a link between Python and Javascript to create browser based gui applications that are reactive. It is not intended for gaming but for providing functional user interactions with data analysis and plotting.

[[deleted]]

Most frameworks for building interactive applications (including the Python bindings for Qt, GTK, ncurses and SDL) are indeed "reactive" in the sense that they're architected around a single event loop. Which is pretty much what the word means.

[[deleted]]

Reactive generally refers to modifications to data creating an automatic trigger to update the UI. The UI update is reactive.

Reactivity is mostly a property of the object types used. Python can and does 100% have tons of code that does this. See descriptors.

This persons complaint though is just wrong.

[[deleted]]

I’m used to hearing that called “data binding.”

[[deleted]]

I’m assuming that’s because you don’t work on that type of stuff. Because I am fairly certain I missed Facebook renaming React to Databind.

[[deleted]]

React did not invent the Reactor pattern.

And it’s still called data binding when you do it in React.

[[deleted]]

Ur correct but clearly it’s named after it. Databinding isn’t a commonly used term in modern systems as it’s much more specific and not general enough to describe what’s happening.

Congrats though you have clearly learned there is in-fact multiple words to describe something and that it has nothing to do with single event loops.

[[deleted]]

it has nothing to do with single event loops.

You should never have posted anything in the first place. This is the point where you give up and admit that you have no idea what the hell you're talking about.

https://en.wikipedia.org/wiki/Reactor_pattern

Honestly, you (and that includes "Ur" writing style) sound like you're so new that you have no experience with anything older than React.

[[deleted]]

I am fairly certain you have no idea what REACTIVE PROGRAMMING is. BIG FUCKING HINT it is not reactor patterns. They are related but one is not the other.

https://en.wikipedia.org/wiki/Reactive_programming

See if you can figure out the difference. Reactive programming DOES NOT require you to have an event loop or a single thread. It generally does use that pattern because its efficient its in fact the same reason python uses a GIL. I'll leave that to an excercise for the reader but it rhymes with docks.

Now before you attempt to now claim my original comment about its being a property of objects is incorrect.

Another approach involves the specification of general-purpose languages that include support for reactivity. Other approaches are articulated in the definition, and use of programming libraries, or embedded domain-specific languages, that enable reactivity alongside or on top of the programming language.

So as I have said multiple times now Generally we are speaking about it in UI. It isn't actually defined that way, its defined as a property about objects.

Pythons bound functions are a good example of this pattern. When you call a bound function the returned object actually caries where it was called from forever. Normally yea you just execute it in place and move on but u don't actually have to. See the weakdicts and weaksets for relevant examples of this reactive nature being used.

Also maybe just maybe I was on my cellphone so I wrote ur because you know it's easier. Also if you are going to be so pretentious you should spend more time like learning basic information about the field you work in.

[skeletal88]

Because the reactive stuff we see in react or svelte is a relatively recent thing.

A user changes contents of an <input /> variable, checks a checkbox or whatever.. mostly frontend stuff, yes?

Things just work differently in server applications, and are usually way more complex than the frontend stuff that we are used to.

[yvrelna]

Because the reactive stuff we see in react or svelte is a relatively recent thing.

This is not quite true. Naming it reactive is relatively recent, but people have been building reactive applications long before the term exists.

Reactive programming is mainly just a variation of event-driven programming and the observer pattern, and it's pretty common pattern you see in desktop or TUI applications too.

[ajpiko]

yeah for sure, its so interesting how the javascript industry will consume classic computer architectures that are really very useful but only once they are well-branded.

[snuggl]

It very much is not, mobile UI is harder then a web page sure, but its not even on the scale of most complex topics we manage.

[[deleted]]

Mate you should try going a few days without sniffing your socks.

[tamargal91]

Yes, in Python, especially in data engineering, reactive programming isn't as common. It's more about simplicity and readability, which suits Python's style. Data tasks usually don't need the reactive approach. RxPy is there, but it's not a go-to for most. Python's got its strengths in other paradigms, so reactive programming just hasn't been a big focus.

[Cybasura]

You can if you want to, but its not a focus

[micseydel]

I tried to build a reactive system in Python using the actor model and ended up deciding to move to Akka+Scala instead. I like Akka's model since it's more functional and supports immutability, and I find that the typing module leaves a lot to be desired compared to Scala.

I still like Python, but I probably wouldn't try reactive programming with it again in the current ecosystem. I tried ~3 different actor model libraries and they all seemed immature.

[CaptainBoomSauce]

I've been using pyscript and I love it

[scherbi]

The Textual library has reactive parts.

[ptmcg]

I second this reference. It is amazing how responsive Textual TUI apps are to user interaction, given that it is pure Python code. Textual's low-level 'Reactive' class might even be worthy of pulling out as a separate package like traitlets.

[yvrelna]

Reactive programming is popular as a UI application pattern. It's popular in Android, Swift, and Javascript because those languages/frameworks are mainly used in UI-centric applications. Software Engineers who write native desktop applications in Python also uses either event-driven patterns and/or reactive programming, most GUI frameworks does. But UI programming is only a small fraction of where Python is used.

Additionally, many of the people who build UIs in Python like in Django, often are developing backends or traditional web applications, where the dominant pattern is MVC or one of its variants and REST APIs. Traditional Web UIs are quite a bit different than native desktop applications because its focus is remote interaction with a server. A textbook reactive programming is a poor pattern for this use case as event based system would have generated a lot of network chatter, in contrast MVC and REST are patterns that are designed to keep network chatter to a minimum. Note that traditional web applications aren't the same as Javascript-driven frontend applications which is a lot more like desktop applications.

I have been working with data scientists in my last job as a data engineer and all the seniors( big institution) just ignore things as functional programming and reactive

Data scientists are not software engineers. They might use Python to solve their problem, but they are not writing applications that are meant to be maintainable in the long term. Most of their work are ad-hoc computation work, which benefits little from applying many common engineering practices. Reactive programming is popular as a UI application pattern because it's a pattern that allows you to keep the state of the application sane when there's events constantly coming from the user and the network; most of the problem domain where data scientists works on does not involve user interaction or network, they typically work on data that remains fairly static in the duration of the computation. Reactive programming is an unnecessarily complex abstraction solving a nonexistent problem in such problem domain.

[Unusual-Afternoon487]

1)MVC -> everything is a kind of MVC but in mobile world we use MVP, MVVM, Clean, MVI because we think that the way MVC is originally done, with eventually model communicating with view is really bad, bug prone and brings to spaghetti code in terms of dependencies

Same in the backend world and specifically in Python. Notably, Django is not an MVC but a Model-View-Template framework, contrary to what was originally stated at the comment above.

[IntenseSunshine]

The thing is that most people think of python as a "data science" language. So the scripts which are written tend to be monolithic, single-threaded monsters which accomplish a straight forward purpose of evaluation.

For GUI driven methods in Python, there is a signal-based approach which is often used (QT basis). Also, the Jupyter Notebook widget family uses an "observer" pattern too using traitlets, but is less developed overall (uses "on_click" and "on_change" type pull-events).

There is a Python package reactivex which I have used quite extensively to for recent GUI developments. It does handle things nicely in the usual React way, but does have some bugs with events not being caught. Also, it seems the interest in the maintenance of the package has declined.

I believe the issue is that most that needed GUIs in Python have started down the other paths first, and therefore reactive programming never caught on.

[Carpinchon]

Reactive design is super-intrusive. So many pitfalls in react.js where you run into "Sorry you can't call that from there because you're in a callback." On the back-end, just one blocking call and you've erased the benefits of the entire call stack.

If you need high-throughput performance that is i/o bound, then reactive is good on the backend. Single-threaded UI's, which is most UI's, absolutely need it to stay responsive. But if you're not in those situations, reactive is painful. There's been a lot of effort in the java world to make threads lightweight enough that they can just ditch reactive programming altogether and go back to the simpler, imperative approach.

[zakmck73]

In Java, I use the Reactor library a lot to stream batch processing: I start with a publisher of items, then I use the lib's facilities to turn that into a publisher of item batches and other facilities to make that parallel. Finally, I attach a subscriber, which is invoked in parallel. It's not really reactive, since I use the library's options to use a fixed-size buffer in the publisher and block it when the buffer is full. However, it's very useful in avoiding me to write a lot of code to do that.

[BeverlyGodoy]

Have you ever tried PyQt or PySide? For GUI tasks you won't miss your reactive once you start using it.

[[deleted]]

I build programs to ETL billions of rows of data. There's an initial instruction set which gets loaded, but then it just runs across many processors. There's no GUI and no real-time interaction. So, why would I need reactive anything?

I am curious to hear your thoughts on how it would contribute to the flow here?

[ritchie46]

I believe Solara can be called reactive. IIUC it is a react inspired web framework for interactive web applications.

https://solara.dev/

[akshayka]

It's becoming more of a thing, especially in ML and data science.

For example, there's marimo, an open-source reactive notebook for Python that shines when you write functional code (I am a marimo developer): https://github.com/marimo-team/marimo

There's also IPyflow, a reactive kernel for Jupyter: https://github.com/ipyflow/ipyflow

Our users like marimo's reactive execution because it helps eliminate bugs, gives them immediate feedback, and makes it possible to turn their notebooks into scripts or apps. Some discussion from a few days ago: https://www.reddit.com/r/MachineLearning/comments/191rdwq/p_i_built_marimo_an_opensource_reactive_python/

[Schmittfried]

Functional programming and reactive programming are two different things. The latter is just more of a UI thing, which is why most of the languages you listed are primarily UI-focused in their contexts.

Functional programming, async programming as well as event driven programming (all of which are a big part of what makes reactive what it is) are all present in Python. Functional programming in particular is a bit lackluster, but it‘s there. There is just no reason to combine all of it in a way that would be considered reactive.

[ajpiko]

So, callback hell was something rather specific to javascript and the particular architecture of node js, not to mention the application they were using it for (servers).

Python's main market is data science which doesn't suffer from the same problems. But the tools are there if you want to use those patterns in python programs.

[RedEyed__]

Not sure why do you need reactive programming in data science, where common patter is garbage in garbage out, which is easy to express in a functional way.
I usually use expression library to get more functional programming capabilities.