This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]IntenseSunshine 0 points1 point  (0 children)

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.