Minor bug fixes and comments to address review.

* Fixed main ipython script.
* Fixed usage of USE_CURSES in completer.py
* Added comment to gui-wx example.

IPython/core/completer.py

@@ -65,12 +65,12 b' used, and this module (and the readline module) are silently inactive.'
 import __builtin__
 import __main__
 import glob
+import itertools
 import keyword
 import os
 import re
 import shlex
 import sys
-import itertools
 import types
 
 from IPython.core.error import TryNext

IPython/core/page.py

@@ -34,7 +34,7 b' import sys'
 from IPython.core import ipapi
 from IPython.core.error import TryNext
 from IPython.utils.genutils import (
-    chop, Term
+    chop, Term, USE_CURSES
 )
 
 if os.name == "nt":

IPython/scripts/ipython

@@ -23,6 +23,6 b' this mode, there is no way to pass IPython any command-line options, as those'
 are trapped first by Python itself.
 """
 
-import IPython.core.ipapi import launch_new_instance
+from IPython.core.ipapi import launch_new_instance
 
 launch_new_instance()

docs/examples/lib/gui-wx.py

@@ -11,6 +11,14 b' Ref: Modified from wxPython source code wxPython/samples/simple/simple.py'
 This example can only be run once in a given IPython session because when 
 the frame is closed, wx goes through its shutdown sequence, killing further
 attempts.  I am sure someone who knows wx can fix this issue.
+
+Furthermore, once this example is run, the Wx event loop is mostly dead, so
+even other new uses of Wx may not work correctly.  If you know how to better
+handle this, please contact the ipython developers and let us know.
+
+Note however that we will work with the Matplotlib and Enthought developers so
+that the main interactive uses of Wx we are aware of, namely these tools, will
+continue to work well with IPython interactively.
 """
 
 import wx