Codify that modules that exist both in Python 2.7 and 3.5 will not be

removed from the stdlib until Python 2.7 is no longer supported.

pep-0004.txt

@@ -2,7 +2,7 @@ PEP: 4
 Title: Deprecation of Standard Modules
 Version: $Revision$
 Last-Modified: $Date$
-Author: Martin von Löwis <martin@v.loewis.de>
+Author: Brett Cannon <brett@python.org>, Martin von Löwis <martin@v.loewis.de>
 Status: Active
 Type: Process
 Content-Type: text/x-rst
@@ -51,6 +51,17 @@ releases that immediately follows the deprecation; later releases may
 ship without the deprecated modules.
 
 
+For modules existing in both Python 2.7 and Python 3.5
+------------------------------------------------------
+
+In order to facilitate writing code that works in both Python 2 & 3
+simultaneously, any module that exists in both Python 3.5 and
+Python 2.7 will not be removed from the standard library until
+Python 2.7 is no longer supported as specified by PEP 373. Exempted
+from this rule is any module in the idlelib package as well as any
+exceptions granted by the Python development team.
+
+
 Procedure for declaring a module undeprecated
 =============================================
 
@@ -258,12 +269,16 @@ Deprecated modules
                    Remove from 2.7
     Documentation: None
 
+    Module name:   imp
+    Rationale:     Replaced by the importlib module.
+    Date:          2013-02-10
+    Documentation: Deprecated as of Python 3.4.
+
     Module name:   formatter
     Rationale:     Lack of use in the community, no tests to keep
                    code working.
-    Documentation: Deprecated as of Python 3.4 by raising
-                   PendingDeprecationWarning. Slated for removal in
-                   Python 3.6.
+    Date:          2013-08-12
+    Documentation: Deprecated as of Python 3.4.
 
 
 Deprecation of modules removed in Python 3.0