<br><br><div class="gmail_quote">On Mon, Dec 14, 2009 at 12:35, Antoine Pitrou <span dir="ltr"><<a href="mailto:solipsis@pitrou.net">solipsis@pitrou.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Steven Bethard <steven.bethard <at> <a href="http://gmail.com" target="_blank">gmail.com</a>> writes:<br>
><br>
> Please read the PEP if you haven't, particularly the "Why isn't the<br>
> functionality just being added to optparse?" section. I don't believe<br>
> it is sensible to re-implement all of optparse. What Ian Bicking is<br>
> proposing, I believe, is simpler -- adding a few aliases here and<br>
> there so that you don't have to rename so many things when you're<br>
> upgrading from optparse to argparse.<br>
<br>
</div>Although I am of the people who think working modules shouldn't be deprecated, I<br>
also don't think adding compatibility aliases is a good idea. They only make the<br>
APIs more bloated and maintenance more tedious. Let's keep the new APIs clean of<br>
any unnecessary baggage.<br></blockquote><div><br></div><div>Ditto from me. If people want a compatible module it can be made available on PyPI for those who want it.</div><div><br></div><div>-Brett </div></div>