Raymond Hettinger <raymond.hettin...@gmail.com> added the comment:
> Sounds like another wet blanket argpment Please watch your tone. It borders on being abusive. It is entirely appropriate to set limits on the scope of what a module is trying to achieve. It is appropriate to consider module learnability. It is appropriate to limit sprawl and feature creep. It is appropriate to consider whether the pattern being encouraged and supported by the PR is intellectually manageable by end users. It is correct that argparse set out to handle more complex cases than optparse. But even then, it was aiming to cases that commonly arose it the wild (subparsers are not uncommon). It never aspired to be all things to all users. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue43046> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
