This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | bethard |
|---|---|
| Recipients | bethard, loewis, orsenthil, rickysarraf |
| Date | 2009年06月10日.14:09:22 |
| SpamBayes Score | 2.4868805e-07 |
| Marked as misclassified | No |
| Message-id | <d11dcfba0906100709p265bec8bu5963758183760470@mail.gmail.com> |
| In-reply-to | <4A2F5696.3050206@v.loewis.de> |
| Content | |
|---|---|
On Tue, Jun 9, 2009 at 11:45 PM, Martin v. Löwis<report@bugs.python.org> wrote: > It would be useful if several people could confirm that argparse > is *not* horribly designed. A totally reasonable request. Anyone willing to evaluate this can take a look at: http://argparse.googlecode.com/svn/trunk/argparse.py It also may help to look at the extensive test suite: http://argparse.googlecode.com/svn/trunk/test/test_argparse.py If anyone has specific questions about how something works or how to extend argparse with new functionality, I'm happy to answer those questions. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009年06月10日 14:09:24 | bethard | set | recipients: + bethard, loewis, orsenthil, rickysarraf |
| 2009年06月10日 14:09:23 | bethard | link | issue6247 messages |
| 2009年06月10日 14:09:22 | bethard | create | |