Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make CLI argparse approach consistent (typer vs argparse) #230

Open
sfmig opened this issue Oct 25, 2024 · 0 comments
Open

Make CLI argparse approach consistent (typer vs argparse) #230

sfmig opened this issue Oct 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@sfmig
Copy link
Collaborator

sfmig commented Oct 25, 2024

Right now some CLI commands use typer (e.g. extract-frames) and some don't (train-detector).

It would be nice to make them consistent.
@sfmig sfmig added the enhancement New feature or request label Oct 25, 2024
@sfmig sfmig changed the title Make CLI argparse approach consistent Make CLI argparse approach consistent (typer vs argparse) Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sfmig