<br><br><div class="gmail_quote">On Sun, Feb 21, 2010 at 13:31, Guido van Rossum <span dir="ltr"><<a href="mailto:guido@python.org">guido@python.org</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">On Sun, Feb 21, 2010 at 1:26 PM, Steven Bethard<br>
<<a href="mailto:steven.bethard@gmail.com">steven.bethard@gmail.com</a>> wrote:<br>
> On Sun, Feb 21, 2010 at 5:45 AM, Guido van Rossum <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:<br>
>> Maybe the best thing is to make optparse *silently* deprecated, with a<br>
>> big hint at the top of its documentation telling new users to use<br>
>> argparse instead, but otherwise leaving it in indefinitely for the<br>
>> benefit of the many existing users.<br>
><br>
> So basically do what the PEP does now, except don't remove optparse in<br>
> Python 3.5? For reference, the current proposal is:<br>
><br>
> * Python 2.7+ and 3.2+ -- The following note will be added to the<br>
> optparse documentation:<br>
> The optparse module is deprecated and will not be developed<br>
> further; development will continue with the argparse module.<br>
> * Python 2.7+ -- If the Python 3 compatibility flag, -3, is provided<br>
> at the command line, then importing optparse will issue a<br>
> DeprecationWarning. Otherwise no warnings will be issued.<br>
> * Python 3.2 (estimated Jun 2010) -- Importing optparse will issue a<br>
> PendingDeprecationWarning, which is not displayed by default.<br>
> * Python 3.3 (estimated Jan 2012) -- Importing optparse will issue a<br>
> PendingDeprecationWarning, which is not displayed by default.<br>
> * Python 3.4 (estimated Jun 2013) -- Importing optparse will issue a<br>
> DeprecationWarning, which is displayed by default.<br>
> * Python 3.5 (estimated Jan 2015) -- The optparse module will be removed.<br>
><br>
> So if I drop that last bullet, is the PEP ready for pronouncement?<br>
<br>
</div>Drop the last two bullets and it's a deal. (OTOH AFAIK we changed<br>
DeprecationWarning so it is *not* displayed by default.</blockquote><div><br></div><div>Yes, DeprecationWarning is now silent under Python 2.7 and 3.1 so a DeprecationWarning would only pop up if developers exposed DeprecationWarning. But if the module is not about to be removed in 3.x then I think regardless of the silence of both warnings it should stay PendingDeprecationWarning.</div>
<div><br></div><div>-Brett</div></div>