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.

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

Move CLI to click #90

Closed
untitaker opened this issue Jul 1, 2014 · 6 comments
Closed

Move CLI to click #90

untitaker opened this issue Jul 1, 2014 · 6 comments

Comments

@untitaker
Copy link
Member

After having used click for some weeks, i can say it is the best CLI framework i've encountered so far.

I think it could eliminate a very large portion of code, mostly due to colorcodes. I also think it would make testing the full application much easier.

@geier
Copy link
Member

geier commented Jul 2, 2014

Sounds good, I'll have a look.

@geier
Copy link
Member

geier commented Jul 8, 2014

I just had a closer look at Click (because I ran into some problems with optparse) and it looks much nicer.

Click it is then.

@geier
Copy link
Member

geier commented Aug 8, 2014

delayed until I find the time to implement [ -a TEXT ... | -b TEXT ... ], which is not currently build-in

@untitaker
Copy link
Member Author

I don't understand, can you elaborate?

@geier
Copy link
Member

geier commented Aug 13, 2014

according to mitsuhiko there is currently no build-in way to make -a
and -b exclusive (using both of them at the same time makes no sense)

Quoting Markus Unterwaditzer (2014-08-12 19:43:13)

I don't understand, can you elaborate?


Reply to this email directly or view it on GitHub:
#90 (comment)

@untitaker
Copy link
Member Author

Fixed with #98.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants