Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cause TypeError: 'NoneType' object is not callable in qtconsole #7049

Closed
khsing opened this issue Nov 28, 2014 · 5 comments
Closed

Cause TypeError: 'NoneType' object is not callable in qtconsole #7049

khsing opened this issue Nov 28, 2014 · 5 comments
Milestone

Comments

@khsing
Copy link

khsing commented Nov 28, 2014

This happens when using qtconsole to display plot

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/IPython/qt/console/frontend_widget.py", line 60, in highlightBlock
    super(FrontendHighlighter, self).highlightBlock(string)
  File "/usr/local/lib/python2.7/site-packages/IPython/qt/console/pygments_highlighter.py", line 115, in highlightBlock
    for token, text in self._lexer.get_tokens(string):
  File "/usr/local/lib/python2.7/site-packages/pygments/lexer.py", line 192, in streamer
    for i, t, v in self.get_tokens_unprocessed(text):
  File "/usr/local/lib/python2.7/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

My environment is OS X 10.10.1, homebrew installed python 2.7.8

$ pip freeze
Jinja2==2.7.3
MarkupSafe==0.23
Pygments==2.0.1
backports.ssl-match-hostname==3.4.0.2
certifi==14.05.14
gnureadline==6.3.3
ipython==2.3.1
matplotlib==1.4.2
mock==1.0.1
nose==1.3.4
numpy==1.9.1
pyparsing==2.0.3
python-dateutil==2.2
pytz==2014.10
pyzmq==14.4.1
scipy==0.14.0
six==1.8.0
tornado==4.0.2
virtualenv==1.11.6
wsgiref==0.1.2
@ccordoba12
Copy link
Member

This was already fixed, see issue #6878. It seems it'll be released in IPython 2.4.

@khsing
Copy link
Author

khsing commented Dec 1, 2014

got it, thanks

@khsing khsing closed this as completed Dec 1, 2014
@dashesy
Copy link

dashesy commented Jan 21, 2015

sorry to ask this here but how often do you update pip? the version there is still 2.3.1 and showing this bug.

@ccordoba12
Copy link
Member

I thought IPython guys were going to release 2.4 quickly but it seems
they are focused now on getting 3.0 out of the door (which this fix too).

So maybe 2.4 is not going to be released after all :-)

El 20/01/2015 a las 08:28 p.m., Ehsan Azar escribió:

sorry to ask this here but how often do you update pip? the version
there is still 2.3.1 and showing this bug.


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

@takluyver
Copy link
Member

2.4 will still happen, probably around the same time as 3.0.

@minrk minrk modified the milestones: no action, 2.4 Jan 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants