Record that PEP 264 resolved some open issues left hanging in 236.

pep-0236.txt

@@ -214,7 +214,7 @@ Standard Module __future__.py
     intended to be enforced starting in release 2.2.
 
 
-Paritally Resolved Problem:  Runtime Compilation
+Resolved Problem:  Runtime Compilation
 
     Several Python features can compile code during a module's runtime:
 
@@ -234,7 +234,8 @@ Paritally Resolved Problem:  Runtime Compilation
     compiles examples taken from strings in M, and those examples should
     use M's choices, not necessarily the doctest module's choices.  In the
     2.1 release, this isn't possible, and no scheme has yet been suggested
-    for working around this.
+    for working around this.  NOTE:  PEP 264 later addressed this in a
+    flexible way, by adding optional arguments to compile().
 
     In any case, a future_statement appearing "near the top" (see Syntax
     above) of text compiled dynamically by an exec, execfile() or compile()
@@ -261,7 +262,7 @@ Resolved Problem:  Native Interactive Shells
     appeared at the top of a module.
 
 
-Unresolved Problem:  Simulated Interactive Shells
+Resolved Problem:  Simulated Interactive Shells
 
     Interactive shells "built by hand" (by tools such as IDLE and the Emacs
     Python-mode) should behave like native interactive shells (see above).
@@ -269,7 +270,11 @@ Unresolved Problem:  Simulated Interactive Shells
     not been exposed, and there isn't a clear way for tools building their
     own interactive shells to achieve the desired behavior.
 
-XXX interactive shell and -i; interactive shell and -c
+    NOTE:  PEP 264 later addressed this, by adding intelligence to the
+    standard codeop.py.  Simulated shells that don't use the standard
+    library shell helpers can get a similar effect by exploiting the
+    new optional arguments to compile() added by PEP 264.
+
 
 Questions and Answers