escapyde VS urwid

Personally I split this up even further nowadays into a separate group for tests (such as here).

The established convention is to have metadata files in the repository root, and the project source code nested a level deeper. escapyde would be a fairly simple example of that.

Well, my GitHub profile is part of my flair in this subreddit, feel free to dig around. My latest project was an attempt to port the ms JavaScript library to Python, and I think I did alright. Other things I can highlight would be my iplib3 package, a server implementation for the EguiValet messaging service, and finally I've got a fairly unfinished text colouring utility called escapyde.

Take my escapyde-project as a small example. The README is at least somewhat helpful, the code files are in a dedicated folder while the root just contains metadata, the dependencies are properly listed in pyproject.toml (could be just requirements.txt in your case, if you want to keep things simple), and the code itself is split across multiple files to make it easier to find what you're looking for. Though admittedly I haven't had time to write proper documentation for it.

Here's one of my own that's pretty small but decently designed: https://github.com/Diapolo10/escapyde

If you'd like some example repos, I have two; escapyde is smaller and probably easier to understand at the moment, whereas iplib3 works as an example for a bigger project. I'm not really one to toot my own horn, but I think they're pretty good as examples so I tend to use them as such.

A while back I made a small library for simplifying ANSI escape sequences, called escapyde, though it's not fully complete as I can't properly chain sequences yet. But it does work, as far as the provided example is concerned.

This year's event has already been good for me, because it gave me the kick I needed to make escapyde (a pet project of mine that aims to make ANSI escape sequences more user-friendly) good enough to work. Reason being that I wanted to use colours to have the answers stand out from my scripts' output, and curses is pretty... cursed on Windows.

Pretty cool! I actually wrote something VERY similar a couple of years ago: sless[1]. It's a tool for viewing json-based structured logs. Just like your tool, you can explore into a json object. The difference is, it expects the input to have many json objects, newline separated, and it shows few keys as a preview of the object, to make looking for something in the log easier. It's not quite complete but basic browsing works. It was mainly written to learn more about Urwid[2], a library similar to Curses.

1: https://github.com/dpedu2/sless

2: https://urwid.org/

In addition to the other great libraries already mentioned, since you're in Python you may want to consider urwid, it's really robust and has a lot of built-ins.

To go full in on the latter case, people often use libraries like Cursive (akin to urwid for Python but without the horrendously confusing error messages caused duck typing) or tui.

Curses seems difficult to use but you should investigate whether it works with what you want to do. https://urwid.org/ seems fun as an alternative.

You can also take a look at https://urwid.org/

urwid is Python, and looks good.

As someone coming from Python, I've had more than enough opaque duck-typed errors from urwid and I'd like my error messages to fit on one page.