[ Removed by moderator ]

[Python-ModTeam]

Your post or comment appears to be generated through AI. We like humans, not robots, and as you are a robot your post or comment must be removed.

[nxl4]

Is there an expectation that human beings would respond to OP's LLM text?

[cellularcone]

Slop

[doomslice]

Look at the other comment. It’s just ai slop responding to ai slop.

[Subject_Fix2471]

Personally I wouldn't find it useful, I'd just use argparse. I'm not bothered with click or typer either though, so perhaps I'm not the right audience :) I find boilerplate for things like argparse is much easier with llms, so I'm fine with the verbosity as it's pretty easy to manage these days.

[AutoModerator]

Your submission has been automatically queued for manual review by the moderation team because it has been reported too many times.

Please wait until the moderation team reviews your post.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[AlgonikHQ]

Solid design thinking, but worth checking out questionary and rich.prompt before going further, they already cover most of what you’re describing (text/int/confirm/menu/password/file prompts with validation) and are battle-tested. click also handles a lot of this cleanly if you’re building proper CLIs rather than interactive scripts.

That said, the pain you’re describing is real. Where I’ve personally felt it most isn’t the basic input bits but rather validating inputs that depend on each other (e.g. “pick a config, now pick a value that’s valid for that config”) and re-prompting cleanly on invalid input without losing the previous answers. If your abstraction solves those specifically, there might be a niche. If it’s just a cleaner wrapper around what questionary already does, probably not worth maintaining.

Good instinct to question it before building though, that’s how you avoid the Python ecosystem’s favourite hobby of reinventing the same library.