##// END OF EJS Templates
runtime warning for possible inputhook collision between pyreadline and qt...
MinRK -
Show More
@@ -17,6 +17,7 b' Inputhook management for GUI event loop integration.'
17
17
18 import ctypes
18 import ctypes
19 import sys
19 import sys
20 import warnings
20
21
21 #-----------------------------------------------------------------------------
22 #-----------------------------------------------------------------------------
22 # Constants
23 # Constants
@@ -183,6 +184,17 b' class InputHookManager(object):'
183 """
184 """
184 from IPython.external.qt_for_kernel import QtCore, QtGui
185 from IPython.external.qt_for_kernel import QtCore, QtGui
185
186
187 if 'pyreadline' in sys.modules:
188 # see IPython GitHub Issue #281 for more info on this issue
189 # Similar intermittent behavior has been reported on OSX,
190 # but not consistently reproducible
191 warnings.warn("""PyReadline's inputhook can conflict with Qt, causing delays
192 in interactive input. If you do see this issue, we recommend using another GUI
193 toolkit if you can, or disable readline with the configuration option
194 'TerminalInteractiveShell.readline_use=False', specified in a config file or
195 at the command-line""",
196 RuntimeWarning)
197
186 # PyQt4 has had this since 4.3.1. In version 4.2, PyOS_InputHook
198 # PyQt4 has had this since 4.3.1. In version 4.2, PyOS_InputHook
187 # was set when QtCore was imported, but if it ever got removed,
199 # was set when QtCore was imported, but if it ever got removed,
188 # you couldn't reset it. For earlier versions we can
200 # you couldn't reset it. For earlier versions we can
General Comments 0
You need to be logged in to leave comments. Login now