[Python-checkins] r57478 - peps/trunk/pep-3002.txt

[alex.martelli]

Author: alex.martelli
Date: Sat Aug 25 21:52:12 2007
New Revision: 57478

Modified:
   peps/trunk/pep-3002.txt
Log:
Fixed option name (-3, not --python3).



Modified: peps/trunk/pep-3002.txt
==============================================================================
--- peps/trunk/pep-3002.txt	(original)
+++ peps/trunk/pep-3002.txt	Sat Aug 25 21:52:12 2007
@@ -78,7 +78,7 @@
 PEP-writing is time-consuming, so when a number of
 backwards-incompatible changes are closely related, they should be
 proposed in the same PEP.  Such PEPs will likely have longer
-Compatibility Issues sections however, since they must now describe
+Compatibility Issues sections, however, since they must now describe
 the sorts of breakage expected from *all* the proposed changes.
 
 
@@ -89,14 +89,14 @@
 Python must also be accompanied by code to issue warnings for pieces
 of Python 2.X code that will behave differently in Python 3000. Such
 warnings will be enabled in Python 2.X using a new command-line
-switch: --python3. All backwards incompatible changes should be
-accompanied by a patch for Python 2.X that, when --python3 is
+switch: -3. All backwards incompatible changes should be
+accompanied by a patch for Python 2.X that, when -3 is
 specified, issues warnings for each construct that is being changed.
 
 For example, if ``dict.keys()`` returns an iterator in Python 3000,
 the patch to the Python 2.X branch should do something like:
 
-    If --python3 was specified, change ``dict.keys()`` to return a
+    If -3 was specified, change ``dict.keys()`` to return a
     subclass of ``list`` that issues warnings whenever you use any
     methods other than ``__iter__()``.