clidantic VS argdantic

I know you want to know it. I chose argparse for two main reasons: first and foremost, this was a personal exercise, as both in-depth look into the standard library and project implementation effort. Second, despite its flaws, argparse remains the go-to choice for many use cases. E.g., from my personal experience in the machine learning field, it's absolutely common to see parsers everywhere. This library is a simple attempt to tidy up and provide a "simpler/cleaner" UX. If you're interested, I also made a click-based version. It is not up to speed with argdantic since I don't use click that much, but it's on my TODO list.

Here's a link to the project, ideas and suggestions are of course welcome: https://github.com/edornd/clidantic

Argdantic tries to merge the powerful features of pydantic with the simplicity and practicality of argparse. Born from my previous experiment (clidantic), argdantic is a natural evolution trying to bring the same concept to argparse, together with some goodies.