new features: Using typer for cli and UV

[franciscosanchezn]

Hi!

I have been recently using this repo and find it really cool. Maybe as a future improvement we can include Typer https://typer.tiangolo.com/ for CLI application.

Also when i clone the repo I find really useful to configure the environment using uv from astral. Maybe that could be another improvement.

what are your thoughts about this?

[p0n1]

Yeah, I like uv and have been using uv in other projects. It's really fast and robust. I was considering about adopting uv for this project. Maybe we should learn the best practices for making UV coexist with the original project. Because I'm afraid of breaking changes.

Thanks for letting me know Typer. Look promising. I will try it in my new projects. What are its notable advantages? I seem to be able to tolerate the original argparse lib.

[franciscosanchezn]

For UV: I used it in several projects too, in my local i added the uv environment for this tool. I think we can add this feature easily, but i am a bit concern because i lack some context (specially because I have only been a user for this repo before, but i want to start contributing).

Related with Typer some advantages is the typing for arguments, but it also offer more cool features like auto-completion. Also they show cool libraries like rich console in their documentation (which by the way is great).

I was thinking about typer for this repo as part of including one CLI per TTS able to easily validate the input args and offer a better user experience. Something like:

epubtoaudio piper create --input [INPUT] --model [MODEL]....
epubtoaudio openai create ...

I have used this in production environments and it is really cool, really easy to create documentation in the cli tool, easy to use and develop...

[p0n1]

Thank you for your interest in contributing. It is definitely welcome! What I care about most is that we try our best not to make breaking changes, because otherwise it would require more effort to develop or review and confuse users.

So, I think we can try uv integration first. We already have a requirements.txt file: https://github.com/p0n1/epub_to_audiobook?tab=readme-ov-file#installation. It would be great if some users can still use that, while others could try using uv.

For Typer, what you proposed is interesting, but it looks like it would require a major refactor of the argument parsing and would change how users interact with this tool. I'm not sure if I understand it correctly.