Update status of some items (mostly deprecated modules)

pep-0361.txt

@@ -61,9 +61,11 @@ Completed features for 2.6
 
     Deprecated modules and functions in the standard library:
 
-        - sets
+        - commands.getstatus()
         - macostools.touched()
+        - popen2, os.popen[234]()
         - posixfile
+        - sets
 
     Modules removed from the standard library:
 
@@ -73,7 +75,10 @@ Completed features for 2.6
 
     Python 3.0 compatability:
 
-        None
+        - warnings were added for the following builtins
+          which no longer exist in 3.0:
+
+             apply, callable, coerce, dict.has_key, execfile, reduce, reload
 
     Other major features:
 
@@ -112,7 +117,7 @@ Possible features for 2.6
           PJE's withdrawal from 2.5 for inclusion in 2.6:
           http://mail.python.org/pipermail/python-dev/2006-April/064145.html
 
-    Module to gain a DeprecationWarning (as specified for Python 2.6
+    Modules to gain a DeprecationWarning (as specified for Python 2.6
     or through negligence):
 
         - rfc822
@@ -124,6 +129,7 @@ Possible features for 2.6
         - sha
         - buildtools
         - cfmfile
+        - compiler package
 
     - warnings module implemented in C
       * Convert Parser/*.c to use warnings module rather than printf
@@ -141,9 +147,6 @@ Possible features for 2.6
       * {}.has_key()
       * All PendingDeprecationWarnings (e.g. exceptions)
       * using zip() result as a list
-      * input()
-      * apply()
-      * reduce()
       * the exec statement (use function syntax)
       * file.xreadlines
       * function attributes that start with func_* (should use __*__)
@@ -167,7 +170,7 @@ Possible features for 2.6
 
     - Replace all old style tests (operate on import) with unittest or docttest
 
-    - All tests for all untested modules
+    - Add tests for all untested modules
 
     - Document undocumented modules/features
 
@@ -196,16 +199,17 @@ Open issues
     http://python.org/sf/1515609
     http://python.org/sf/1515361
 
-    How should -m (and __main__ in general) work with relative imports?
+    How should -m (__main__ in general) work with relative imports? [#pep366]_
-    http://mail.python.org/pipermail/python-dev/2006-June/066161.html
-    (also see the section on main modules in PEP 338)
 
 
 References
 
-    [1] Adding a __dir__() magic method
+.. [1] Adding a __dir__() magic method
    http://mail.python.org/pipermail/python-dev/2006-July/067139.html
 
+.. [#pep366] PEP 366 (Main module explicit relative imports)
+   http://www.python.org/dev/peps/pep-0366
+
 
 Copyright