Ctrl+I doesn't seem to work on the editor on current tree on Windows

[stonebig]

Description of your problem

What steps will reproduce the problem?

1. open spyder
2. type "print" in the editor then Ctrl+I
3. the help window becomes blank
4. type "print" in the qtconsole of spyder then Ctrl+I
5. the help window shows the description of print function

is it normal nothing shows up at step 3?

Versions and main components

• Spyder Version: tree of 2015-03-11 19h00 GMT
• Python Version: 3.4
• Operating system: Windows 7 64bit , Python 3.4.1

Dependencies

jedi >=0.8.1 : 0.9.0 (OK)
matplotlib >=1.0: 1.5.1 (OK)
nbconvert >=4.0 : 4.1.0 (OK)
numpy >=1.7 : 1.10.4 (OK)
pandas >=0.13.1 : 0.18.0rc2 (OK)
pep8 >=0.6 : 1.7.0 (OK)
pyflakes >=0.6.0: 1.1.0 (OK)
pygments >=1.6 : 2.1.3 (OK)
pylint >=0.25 : 1.5.4 (OK)
qtconsole >=4.0 : 4.2.0 (OK)
rope >=0.9.4 : 0.9.4-1 (OK)
sphinx >=0.6.6 : 1.3.6 (OK)
sympy >=0.7.3 : 1.0 (OK)

[stonebig]

it was ok with beta2 in previous WinPython ... I'm a little lost on the root cause of this

import numpy as np
np.s

doesn't propose the possible "s" function either. (again in the editor only)

[stonebig]

hum, either I just mistaken, either it works again with latest comit... strange

[ccordoba12]

Great! We changed the internals of our completion machinery (in pull request #3049), so that could be the reason why this is working again! :-)

[stonebig]

On the other end, starting the new spyder:

• failed today (it was alongside the old, could there be a relationship ?)
• doesn't restart (i see a pythonw process pending) .
• after killing pythonw, it's okay again, except there is nothing in the qtconsole..

Any suggestion to get the qtconsole back ?
Is there a conflict with jupyter-qtconsole ?

... after a jupyter-qtconsole start (and stop), and a spyder re-start, it's ok again....

==> something seems not stable in yesterday comit

[stonebig]

It seems a pythonw process continues to run when I stop (red cross on top right) a Spyder_launched_with_async_server, on Windows

[RobertPeetsalu]

This bug is still in production though it's closed. I'm reproducing the exact same steps that are in the bug description. Should I make a new issue?

Version and main components

• Spyder Version: 3.1.2
• Python Version: 3.6.0
• Qt Versions: 5.6.2, PyQt5 5.6 on Windows

Dependencies

pyflakes >=0.6.0 :  1.5.0 (OK)
pep8 >=0.6       :  1.7.0 (OK)
pygments >=2.0   :  2.1.3 (OK)
qtconsole >=4.2.0:  4.2.1 (OK)
nbconvert >=4.0  :  4.2.0 (OK)
pandas >=0.13.1  :  0.19.2 (OK)
numpy >=1.7      :  1.11.3 (OK)
sphinx >=0.6.6   :  1.5.1 (OK)
rope >=0.9.4     :  0.9.4-1 (OK)
jedi >=0.8.1     :  0.9.0 (OK)
matplotlib >=1.0 :  2.0.0 (OK)
sympy >=0.7.3    :  1.0 (OK)
pylint >=0.25    :  1.6.4 (OK)

[CoderCoderCoder]

Same problem with 3.1.4 on MacOS 10.12.5. Spyder installed through Anaconda. Initially it worked, but then suddenly I have exactly the same problems:

• "Editor" help window remains blank
• the input area is disabled
• "Automatic import" checkbox is greyed out

For "Console" everything works fine.
Code autocompletion also doesn't work anymore (e.g. typing a "." after a class doesn't show any methods.

Please help, thanks.

jedi >=0.9.0 : 0.10.2 (OK)
matplotlib >=1.0 : 2.0.2 (OK)
nbconvert >=4.0 : 5.1.1 (OK)
numpy >=1.7 : 1.13.1 (OK)
pandas >=0.13.1 : 0.20.3 (OK)
pep8 >=0.6 : 1.7.0 (OK)
psutil >=0.3 : 5.2.2 (OK)
pyflakes >=0.6.0 : 1.5.0 (OK)
pygments >=2.0 : 2.2.0 (OK)
pylint >=0.25 : 1.6.4 (OK)
qtconsole >=4.2.0: 4.3.0 (OK)
rope >=0.9.4 : 0.9.4-1 (OK)
sphinx >=0.6.6 : 1.5.6 (OK)
sympy >=0.7.3 : 1.0 (OK)

P.S. I had to set export EVENT_NOKQUEUE=1 , as I got some warning about queue and read about the solution by defining this variable. But I guess this has no connection to the issue described above, as the error was also before setting this variable.

[CoderCoderCoder]

OK, I solved this problem by myself. Uninstalled Jedi 0.10.2, installed Jedi 0.9.0.
To bad that this is only visible in Spyder 3.1.3 (I have installed the previous version by testing what happens then), it thrown the warning about Jedi version mismatch. In Spyder 3.1.4 there is no such warning. Moreover, in Spyder 3.1.4 this workaround doesn't help, so I stayed with 3.1.3.

[adithyavarambally]

@CoderCoderCoder it didnt work for me tho

[endolith]

Problem has returned in 3.3.1

[Chisuz]

i concur. 3.3.1 has the same issue, ctrl+i will only work from the console.

PLUS for me, the online help panel will always return "Unable to load page" on whatever item i select from the module index ... do you have any suggestions on this?

[arnav1307]

Same even i am facing the same problem