camply VS quick

Adding Textual support to camply [1] was apparently very easy. I didn't to the implementation; I just contribute to the project sometimes: https://juftin.com/camply/command_line_usage/#tui

[1] https://juftin.com/camply/

I've got an open-source project called camply. Here's the spiel:

I've built a free command line tool that helps with this - it's called camply: https://juftin.com/camply.

Here's a personal page built with Jekyll: https://juftin.com. And here's a Sphinx Page: https://juftin.com/camply. Both are actually hosted on GitHub pages for free.

I used this one once, but it only does campsite availability.

I came across a reddit post about a really neat tool somebody created to find openings at campgrounds on the recreation.gov website (after cancellations) and get notified immediately. This does not secure you the reservation, but instead uses the website's (public) API to link you to the booking page, from which you then select those dates that somebody else cancelled. It looks like this.

If you have a working understanding of how to run the below command and then your command line proficiency is likely enough to work with camply and you can feel free to start a discussion on GitHub to ask questions: https://github.com/juftin/camply/discussions

Which is arguably a good reason Click should look for an alternative basis (though, OTOH, the reasons Click remains on optparse are, arguably, a reason that optparse, while it perhaps should not be further developed but for bug fixes, should not be considered deprecated), but in fact a lot of Python command-line programs depend on Click, so something that only works on argparse-based programs does not, in fact, support "almost any Python command line program".

Interestingly, there is a gooey-inspired GUI generator for Click-based programs: https://github.com/szsdk/quick

I might give this a go https://github.com/szsdk/quick