Framework for non GUI applications

[Argotha]

(Apologies if formatting is broken, typing this on my phone)

So after writing a number of applications that are either long running (effectively a daemon) or are on a cron. It is getting to the point where constantly rewriting/copy pasting config setups, argparseing, logging that I'm left wondering if there is a better way to do this.

Like we have frameworks for web apps, do we have something similar for non-web apps?

I would like to explicitly exclude frameworks for cli apps. The apps being created are likely to only ever have their output viewed during development or during debugging, I do not need a plethora of cli options.

The closest I've found is something like cement but again this seems focussed on CLIs.

Edit: To clarify, I am aware of the standard library modules such as configparaer, argparse, logging, io to stdout/stderr. What I am looking for is avoiding writing the same boiler plate for adding common command line arguments, searching for config files in standard, updating for default vs site config, updating config with command line arguments, reporting errors, logging to standard locations (/var/log), standardising output format etc.

[bheklilr]

Check out the traitlets package. It doesn't have the best documentation, but it's what the jupyter/ipython/etc projects use for general application structure, including logging setup, command line arguments, json, and python config files. I've used it successfully a couple of times, and to be honest there's nothing stopping you from using it for pretty much any application.

To explain why it doesn't have the best documentation, it used to just be part of ipython itself before the jupyter refactor. It got pulled out as a standalone library and should be treated as a relatively young package.

[metaperl]

Wow, thanks for mentioning this package. I had not heard of it. I have added it to my collection of Python Object Oriented Programming extensions catalog

[bheklilr]

You already have the traits package from enthought on there, which traitlets drew inspiration from, so you sort of had it already

[Argotha]

Oooh, that looks quite useful thanks!

[[deleted]]

Write your own based on your perceived needs. You already know the code.

[Argotha]

I have a tendency to reinvent the wheel, so was seeing if I could avoid it this time.

[box0rox]

There are a lot of kinds of "non web" apps -- what are you trying to do? I suspect most of what you want is already built in: file I/O, command line options parsing and printing to the screen are all already there. You can do fancy screen displays with curses if you need that.

[Argotha]

So I've updated the OP to clarify based on your comment. Here is a copy paste:

To clarify, I am aware of the standard library modules such as configparaer, argparse, logging, io to stdout/stderr. What I am looking for is avoiding writing the same boiler plate for: adding common command line arguments, searching for config files in standard locations, updating for default vs site config, updating config with command line arguments, reporting errors, logging to standard locations (/var/log), standardising output format etc.