backend VS asciimatics

Shameless appeal for code commentary review:

This reminds me of a code comment I wrote about some web crawling code that is intended to maintain a continuous web address "flow graph", matching any origin URL(s) (the 'water table' of a web page) down to the current location of that page on the web (the 'river delta').

This can be complicated because old URLs may be redirected (HTTP 301, 302) to different locations over time, often for SEO reasons or due to change of domain ownership.

Does the code comment linked below make sense? I'd really appreciate any feedback and improvements:

https://github.com/openculinary/backend/blob/5116c4f5d39dae1...

(and yes, I realize the ASCII art here pales in comparison to some of the visually appealing and clear diagrams shared in the article. I'm doing my best :))

For small apps, I may choose a TUI (Terminal User Interface). Curses for Python is very lightweight, but quite low level and difficult to use for anything more than a very simple interface (if your app tries to draw outside of the drawing area, the app crashes, so you have to carefully manage every detail). Textual and asciimatics are both mature TUI frameworks that provide a higher level and more Pythonic way to create TUI's.

If you are looking for something more flexible that just printing to a terminal, take a look at Asciimatics and textual. Both are available from Pypi.

Scroll down to the TUI example in the README, just above the documentation link: https://github.com/peterbrittain/asciimatics

Download fireworks.py

Source code: https://github.com/peterbrittain/asciimatics/blob/master/samples/fireworks.py

I have made yet another ssh connection manager with TUI, using asciimatics and tinyDB.

Personally I dig the aesthetics of asciimatics, it's quite handy and cross-platform.

I've used asciimatics in the past to good effect.

Take a look at rich (kinda new, but pretty neat), asciimatics, or urwid