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 ncoghlan
Recipients bethard, ncoghlan, python-dev, sandro.tosi, techtonik
Date 2011-03-26.15:14:50
SpamBayes Score 0.00023566131
Marked as misclassified No
Message-id <AANLkTi=d875YNtOwo6KCEx_YFJjZ4PVHg3+w0w9tSeT7@mail.gmail.com>
In-reply-to <AANLkTikFVqAD_pys1sHatshSEUDBaPXeUBs+X1i1R3rs@mail.gmail.com>
Content
On Sat, Mar 26, 2011 at 9:14 PM, anatoly techtonik <techtonik@gmail.com> wrote:
> A pity that before argparse replaced optparse, there was no research
> made to gather the output from various console tools to see how
> argparse really saves people from reinventing their solutions.

argparse was adopted because it was a significant improvement over
optparse, not because anyone was under the illusion that it was
perfect.

There'll always be room for additional feature requests, and many of
them won't cause backwards compatibility problems.

Cheers,
Nick.
History
Date User Action Args
2011-03-26 15:14:50ncoghlansetrecipients: + ncoghlan, bethard, sandro.tosi
2011-03-26 15:14:50ncoghlanlinkissue7284 messages
2011-03-26 15:14:50ncoghlancreate