[Python-checkins] r78294 - peps/trunk/pep-0389.txt

steven.bethard python-checkins at python.org
Sun Feb 21 19:54:45 CET 2010


Author: steven.bethard
Date: Sun Feb 21 19:54:45 2010
New Revision: 78294

Log:
Adjust optparse deprecation strategy as per Guido's request (no actual removal of optparse) and mark PEP as accepted.

Modified:
   peps/trunk/pep-0389.txt

Modified: peps/trunk/pep-0389.txt
==============================================================================
--- peps/trunk/pep-0389.txt	(original)
+++ peps/trunk/pep-0389.txt	Sun Feb 21 19:54:45 2010
@@ -1,9 +1,9 @@
 PEP: 389
-Title: argparse - new command line parsing module
+Title: argparse - New Command Line Parsing Module
 Version: $Revision$
 Last-Modified: $Date$
 Author: Steven Bethard <steven.bethard at gmail.com>
-Status: Draft
+Status: Accepted
 Type: Standards Track
 Content-Type: text/x-rst
 Created: 25-Sep-2009
@@ -136,8 +136,10 @@
 Deprecation of optparse
 =======================
 Because all of optparse's features are available in argparse, the
-optparse module will be deprecated. The following very conservative
-deprecation strategy will be followed:
+optparse module will be deprecated. However, because of the
+widespread use of optparse, the deprecation strategy contains only
+documentation changes and warnings that will not be visible by
+default:
 
 * Python 2.7+ and 3.2+ -- The following note will be added to the
   optparse documentation:
@@ -149,23 +151,10 @@
   provided at the command line, then importing optparse will issue a
   DeprecationWarning. Otherwise no warnings will be issued.
 
-* Python 3.2 (estimated Jun 2010) -- Importing optparse will issue
-  a PendingDeprecationWarning, which is not displayed by default.
+* Python 3.2+ -- Importing optparse will issue a
+  PendingDeprecationWarning, which is not displayed by default.
 
-* Python 3.3 (estimated Jan 2012) -- Importing optparse will issue
-  a PendingDeprecationWarning, which is not displayed by default.
-
-* Python 3.4 (estimated Jun 2013) -- Importing optparse will issue
-  a DeprecationWarning, which *is* displayed by default.
-
-* Python 3.5 (estimated Jan 2015) -- The optparse module will be
-  removed.
-
-Though this is slower than the usual deprecation process, with two 
-releases of PendingDeprecationWarnings instead of the usual one, it
-seems prudent to avoid producing any casually visible Deprecation
-warnings until Python 3.X has had some additional time to attract
-developers.
+Note that no removal date is proposed for optparse.
 
 
 Updates to getopt documentation


More information about the Python-checkins mailing list