Apparently in some cases cursor.selectedText() can return None instead of an empty
string (Scientific Linux 6.0 being only reported case). Relax logic using this method,
so string methods are only called when the string is not empty.
Should fix #724
+1, correct logic, thanks for fixing this. Merge away.
Since your message doesn't say 'closes gh-724' you may need to do it manually, I don't know if gh will identify 'fix #724' as well.
the actual commit message does have the 'closes' text. The commit parser is pretty greedy, though - I have had it auto-close Issues I only mentioned.
Ah, got it. Good to know, thanks.
It doesn't seem appropriate to merge this. Please see the discussion in #724, in which the user reports further problems.
Yes, either we need to place a bound on our PyQt version dependency, or fix every string check to allow for None.
Fair enough, but what version? Do we just guess that 4.7.0 resolves the issue? I see no evidence of this change in the pyqt docs, and I'm certainly not going to build a bunch of PyQt versions to find out.
Should we make the PySide import version check as well, since early dev versions are known to not work?
There's also the hilarious fact that I have no idea how to find out the PyQt version from Python...
@fperez I don't know which versions of PyQt have this bug, sorry. It may be worth posting to their mailing list. For PySide, I think that versions 1.0.3+ work with IPython.
@minrk It's not very well advertised, but this works:
from PyQt4 import QtCore
QtCore.QT_VERSION, QtCore.QT_VERSION_STR # Qt version info
QtCore.PYQT_VERSION, Qtcore.PYQT_VERSION_STR # Binding version info
version check Qt bindings in external.qt
require PySide >= 1.0.3 or PyQt4 >= 4.7
Thanks, @epatters, it would have taken me a long time to find that.
I just redid this branch, so that it only adds version checks to external.qt, so the frontend won't try to start with PyQt < 4.7 or PySide < 1.0.3.
Well, this looks good to me. Thanks, Min.
@rajeeja: Hi, welcome to IPython. The best thing for this sort of problem is to join the ipython-user mailing list and ask for help there - that way more people will see your question. http://mail.scipy.org/mailman/listinfo/ipython-user