forgo VS atbswp

ForgoJS: a 4KB React alternative that gets rid of framework specific DOM access techniques and state management. For example: let people use closures for managing component state rather than something new like hooks.

Here's a preview: https://github.com/forgojs/forgo

I'll do a Show HN once it's ready.

This book is definitely a good starting point, and if you want a glimpse of what you can achieve with an automation library (pyautogui in the case of the book), do check out atbswp

Using the library of the author pyautogui, I developed a macro recorder atbswp (Yes like the book) which makes it very easy to automate boring tasks, do check it out.

Seems I am late to the party. Anyway, if you like automation, check out atbswp

Shameless plug, you can do the same with this[0] albeit not in the CLI.

0: https://github.com/rmpr/atbswp

Source: I use both in a project of mine atbswp

I just released a new version of atbswp I intend to start working on the v0.3 (or 0.2.1 not sure yet)

Just to add options on top of QT5, there's also wxPython. It's pretty good, and fwiw, I use it for this project not the most convoluted GUI out there but it works. Iirc there's also Pysimplegui but I never used it.

Not necessarily, you can use a CI pipeline to verify that your project can be build with many Python versions. This is the workflow I use here[0]. It makes catching and fixing breaking changes easier. Plus, I'm confident the core team is not likely to introduce a painful breaking change (think Python 2 -> 3) soon[1]

0: https://github.com/rmpr/atbswp

1: https://mobile.twitter.com/gvanrossum/status/130608247244308...