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

argparse, too convoluted? #3

Open
nteetor opened this issue Oct 28, 2016 · 1 comment
Open

argparse, too convoluted? #3

nteetor opened this issue Oct 28, 2016 · 1 comment
Labels

Comments

@nteetor
Copy link
Collaborator

nteetor commented Oct 28, 2016

As I look through argparse I wonder if restrictions in Python required the creation of so many formal classes. I do not know what challenges the developer came across while building argparse. If I did I might be able to better reason the use of formal classes.

If we move forward we may very well discover the same problems argparse did and end up needing specialized classes. To begin with I would focus on a single class to contain how the user wishes parsing to happen. We may need a parser class to carry out the actual parsing, but I could see a function working just as well to begin with.

Also, this bewest/argparse#9.

@travisbyrum
Copy link
Owner

Right now I am thinking about a general Parser class and then just having functions that add attributes to the parser object.

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

No branches or pull requests

2 participants