qtconsole problems with pygments

[thomas-haslwanter]

On a 64-bit Win7-Professional (SP1) I have tried different WinPython 3.4.2.3 releases (the 64-bit release, as well as the 32-bit FlavorKivy release), which ship with ipython 2.3.1, and both lead to the following problem:
When I

• Start a WinPython command-prompt
• then run "ipython qtconsole"
• and then type "from" on the ipython commandline,

then the command-prompt Console shows the errormessage printed below. Ipython keeps on running, and the error does not seem to be critical.

Errormessage:

Traceback (most recent call last):
File "C:\WinPython-64bit-3.4.2.3\python-3.4.2.amd64\lib\site-packages\IPython\qt\console\frontend_widget.py", line 60, in highlightBlock
super(FrontendHighlighter, self).highlightBlock(string)
File "C:\WinPython-64bit-3.4.2.3\python-3.4.2.amd64\lib\site-packages\IPython\qt\console\pygments_highlighter.py", line 115, in highlightBlock
for token, text in self._lexer.get_tokens(string):
File "C:\WinPython-64bit-3.4.2.3\python-3.4.2.amd64\lib\site-packages\pygments\lexer.py", line 192, in streamer
for i, t, v in self.get_tokens_unprocessed(text):
File "C:\WinPython-64bit-3.4.2.3\python-3.4.2.amd64\lib\site-packages\IPython\qt\console\pygments_highlighter.py", line 30, in get_tokens_unprocessed
for item in action(self, m):
TypeError: 'NoneType' object is not callable

If you suspect this is an IPython bug, please report it at:
https://github.com/ipython/ipython/issues
or send an email to the mailing list at ipython-dev@scipy.org

You can print a more detailed traceback right now with "%tb", or use "%debug"
to interactively debug it.

Extra-detailed tracebacks for bug-reporting purposes can be enabled via:
c.Application.verbose_crash=True

[ccordoba12]

This was fixed in PR #6878. It will be released (I think) in IPython 2.4

Spyder included this patch in its 2.3.2 version.

[damianavila]

It will be released (I think) in IPython 2.4

We are going to 3.0, there is no current plan for a IPython 2.4 😉

[ccordoba12]

I saw a 2.4 label around, so... ;-)

El 19/12/14 a las 18:38, Damián Avila escribió:

It will be released (I think) in IPython 2.4

We are going to 3.0, there is no current plan for a IPython 2.4 😉

—
Reply to this email directly or view it on GitHub
#7272 (comment).

[takluyver]

We are planning 2.4 - we will backport the nbformat changes so it can read nbformat v4 files (but it will still save in v3 by default).

[damianavila]

well... now I am doubting... ja ja... but from the last meetings I don't remember a 2.4 discussion (I lost some meeting in Nov, maybe it was discussed there).

[damianavila]

Thanks @takluyver for the clarification... probably I missed that discussion.