pycopy VS picotui

Oh, so you're interested to get 100 tomes of technical drawings for SpaceX? You may be out of luck with it, but with any open-source project you're in luck - source to answer all of your questions is right there ;-). https://github.com/pfalcon/pycopy in this case. There's also the testsuite which formally specifies everything Pycopy can do (coverage 97%): https://github.com/pfalcon/pycopy/tree/master/tests . Finally, the docs include the section on specific differences with CPython3.4: https://pycopy.readthedocs.io/en/latest/differences/index.html (but that's human-written, so definitely not complete). By the way, docs are 381 pages rendered as a PDF: https://pycopy.readthedocs.io/_/downloads/en/latest/pdf/ .

Really? Here's direct link to the closest subsection header: https://github.com/pfalcon/pycopy/#the-unix-version , and quoting it here for you:

Well, here it is: https://github.com/pfalcon/pycopy/blob/master/py/vm.c#L367

https://github.com/pfalcon/pycopy/tree/v3.5.0 (if you prefer to drop people into the code, since the release URL does not contain release notes)

pycopy – a minimalist and memory-efficient Python dialect

It's great to see some more competitors on the TUI front of the Python ecosystem! I recently tried multiple existing frameworks and was not particularly happy with the state.

Here are the main contenders for libraries that provide higher-level API than urwid/ncurses:

* Picotui, https://github.com/pfalcon/picotui

* Npyscreen, https://github.com/npcole/npyscreen

* py_cui, https://github.com/jwlodek/py_cui

Both Picotui and Npyscreen are relatively unmaintained / considered feature-full. py_cui seems to be in the best shape.

Fingers crossed for this project making it through, building on top of Rich gives it quite a bit of headstart. You can also sponsor @willmcgugan on Github [0].

[0]: https://github.com/sponsors/willmcgugan

test - use a TUI if you don't want line based, like picotui