spyder-ide / spyder

Official repository for Spyder - The Scientific Python Development Environment
https://www.spyder-ide.org
MIT License
8.32k stars 1.61k forks source link

Editor autocompletion and help extraction not working in Spyder 3.1.4 #4410

Closed jrast closed 7 years ago

jrast commented 7 years ago

I have updated Spyder (pip install -U spyder) to 3.1.4 and the autocompletion in the editor stopped working. In the IPython console it's still working, but not in the editor.

Please provide any additional information below

Dependencies

jedi >=0.9.0 : 0.10.2 (OK) matplotlib >=1.0 : 2.0.0 (OK) nbconvert >=4.0 : 5.1.1 (OK) numpy >=1.7 : 1.11.3 (OK) pandas >=0.13.1 : 0.19.2 (OK) pep8 >=0.6 : 1.7.0 (OK) pyflakes >=0.6.0 : 1.5.0 (OK) pygments >=2.0 : 2.2.0 (OK) pylint >=0.25 : 1.7.1 (OK) qtconsole >=4.2.0: 4.3.0 (OK) rope >=0.9.4 : 0.9.4-1 (OK) sphinx >=0.6.6 : 1.5.5 (OK) sympy >=0.7.3 : None (NOK)

ccordoba12 commented 7 years ago

@dalthviz, please take a look at this one. Notice that the OP has Jedi 0.10.2 installed.

jrast commented 7 years ago

Ok, after several restarts of Spyder, it's seems like it's working sometimes but not always. Kind of hard to say when it's working and when not.

I will update the issue as soon as I can see some pattern.

BjornFJohansson commented 7 years ago

got this too, downgraded to 0.9.0 from 0.10.0 and it came back.

minzheguo commented 7 years ago

I got the same issue. Changing jedi version didn't work for me. Downgrading spyder from 3.1 to 3.0 worked for me.

stonebig commented 7 years ago

could it be a timeout issue ? on a too slowed computer, jedi abort itself ?

ccordoba12 commented 7 years ago

Is this only happening on Windows for you guys?

minzheguo commented 7 years ago

I re-updated the Spyder to the 3.1.4 version. But the autocompletion didn't work again in the editor (nothing showed up after waiting for about almost 1 minute).

Then I re-downgraded the Spyder to 3.0.2, and it worked again. The code-completion showed up immediately after I typed "numpy." or pressed short-cut. Next, I tested spyder 3.1.0 and 3.1.2. They worked as well as 3.0.2.

When I tested spyder 3.1.3. A missing dependency error message showed as follows: jedi =0.9.0: 0.10.2 (NOK) I ignored the error message, and the autocompletion still worked.

Finally, I updated spyder to 3.1.4 again, and the autocompletion didn't work.

The tests were run on a windows 7 x64 PC. Used the spyder 3 for Python 3.5 installed through conda. Haven't tested other environments.

Hope these help!

Some more information about my environment:

Python 3.5.2 :: Anaconda custom (64-bit)

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

stonebig commented 7 years ago

on my old pc, spyder3.2.0dev2017-05-11:

in the past, hot restart were quick,

jrast commented 7 years ago

Note that in the IPython console and Python console, the autocompletion works as expected and is quite responsive. For numpy / matplotlib the completion is available with no notable delay. The problem exists only in the editor window.

ccordoba12 commented 7 years ago

I can't reproduce this in an Anaconda environment with all packages up to date. There was a problem with the Jedi conda package (one of our completion libraries) but it was solved on Sunday, so people using Anaconda please update Jedi with

conda update jedi

I also tested this with all pip packages (inside a conda env because I can't do it otherwise, but the env only provides Python and pip as base packages) and everything is fine there too.

So I don't know what happens in your case, sorry.

ccordoba12 commented 7 years ago

Packages for pip are also all up to date.

ccordoba12 commented 7 years ago

Downgraded Jedi to 0.9.0 -> Spyder Crashed on each startup (even after spyder --reset)

For this to work you also need to downgrade IPython because it now depends on Jedi too. That's where the crash comes from.

FuZhiyu commented 7 years ago

jedi >=0.8.1 : 0.9.0 (OK) matplotlib >=1.0 : None (NOK) nbconvert >=4.0 : 5.1.1 (OK) numpy >=1.7 : None (NOK) pandas >=0.13.1 : None (NOK) 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 : None (NOK)

Here is my dependency. I'm running on MacOS Sierra. I've tried all versions of jedi and spyder available, but no one works.

I give up now. TAT

BjornFJohansson commented 7 years ago

I run on ubuntu like this and it seems to work

``` (bjorn3) bjorn@bjorn-ThinkPad-T450s:~$ conda list # packages in environment at /home/bjorn/anaconda3/envs/bjorn3: # _license 1.1 py35_1 defaults alabaster 0.7.9 py35_0 defaults anaconda custom py35_0 defaults anaconda-clean 1.1.0 py35_0 defaults anaconda-client 1.6.2 py35_0 defaults anaconda-navigator 1.5.1 py35_0 defaults anaconda-project 0.4.1 py35_0 defaults appdirs 1.4.3 py35_0 conda-forge argcomplete 1.0.0 py35_1 defaults args 0.1.0 py35_0 conda-forge arrow 0.8.0 py35_0 conda-forge astroid 1.4.9 py35_0 defaults astropy 1.3 np111py35_0 defaults babel 2.3.4 py35_0 defaults backports 1.0 py35_0 defaults backports.shutil_get_terminal_size 1.0.0 py35_0 conda-forge beautifulsoup4 4.5.3 py35_0 defaults binaryornot 0.4.0 py35_1 conda-forge biopython 1.68 np111py35_0 defaults bitarray 0.8.1 py35_0 defaults blaze 0.10.1 py35_0 defaults bleach 1.5.0 py35_0 conda-forge blinker 1.4 py35_0 conda-forge bokeh 0.12.4 py35_0 defaults boto 2.45.0 py35_0 defaults bottleneck 1.2.0 np111py35_0 defaults cachetools 2.0.0 py35_0 conda-forge cairo 1.14.8 0 defaults cffi 1.9.1 py35_0 defaults chardet 2.3.0 py35_0 defaults chest 0.2.3 py35_0 defaults click 6.7 py35_0 defaults clint 0.5.1 py35_0 conda-forge cloudpickle 0.2.2 py35_0 defaults clyent 1.2.2 py35_0 defaults cobra 0.5.11 collective.checkdocs 0.2 colorama 0.3.7 py35_0 defaults configobj 5.0.6 py35_0 defaults contextlib2 0.5.4 py35_0 defaults cookiecutter 1.5.0 py35_0 conda-forge coverage 4.3.4 py35_0 defaults cryptography 1.7.1 py35_0 defaults curl 7.52.1 0 defaults cycler 0.10.0 py35_0 defaults cython 0.25.2 py35_0 defaults cytoolz 0.8.2 py35_0 defaults dask 0.13.0 py35_0 defaults datashape 0.5.4 py35_0 defaults dbus 1.10.10 0 defaults decorator 4.0.11 py35_0 defaults dill 0.2.5 py35_0 defaults docopt 0.6.2 py35_0 defaults docutils 0.13.1 py35_0 defaults dropbox 6.9.0 dynd-python 0.7.2 py35_0 defaults entrypoints 0.2.2 py35_1 defaults et_xmlfile 1.0.1 py35_0 defaults expat 2.1.0 0 defaults ezodf 0.3.2 py35_0 openglider fastcache 1.0.2 py35_1 defaults feedgenerator 1.9 py35_0 conda-forge filelock 2.0.6 py35_0 defaults flask 0.12 py35_0 defaults flask-cors 3.0.2 py35_0 defaults fontconfig 2.12.1 2 defaults freetype 2.5.5 2 defaults future 0.15.2 py35_0 defaults get_terminal_size 1.0.0 py35_0 defaults gevent 1.2.1 py35_0 defaults ghp-import 0.5.5 py35_0 conda-forge glib 2.50.2 1 defaults gmp 6.1.1 0 conda-forge greenlet 0.4.11 py35_0 defaults gst-plugins-base 1.8.0 0 defaults gstreamer 1.8.0 0 defaults h5py 2.6.0 np111py35_2 defaults harfbuzz 0.9.39 2 defaults hdf5 1.8.17 1 defaults heapdict 1.0.0 py35_1 defaults html5lib 0.999 py35_0 defaults icu 54.1 0 defaults idna 2.2 py35_0 defaults imagesize 0.7.1 py35_0 defaults ipykernel 4.6.1 py35_0 defaults ipython 6.0.0 py35_0 defaults ipython_genutils 0.2.0 py35_0 defaults ipywidgets 6.0.0 py35_0 defaults isort 4.2.5 py35_0 defaults itsdangerous 0.24 py35_0 defaults jbig 2.1 0 defaults jdcal 1.3 py35_0 defaults jedi 0.9.0 py35_1 defaults jinja2 2.9.4 py35_0 defaults jinja2-time 0.1.0 py35_0 conda-forge jpeg 9b 0 defaults jsonschema 2.5.1 py35_0 defaults jupyter 1.0.0 py35_3 defaults jupyter_client 5.0.1 py35_0 defaults jupyter_console 5.1.0 py35_0 defaults jupyter_core 4.3.0 py35_0 defaults jupytercontrib 0.0.6 jupyterlab 0.19.0 py35_0 conda-forge lazy-object-proxy 1.2.2 py35_0 defaults libdynd 0.7.2 0 defaults libffi 3.2.1 1 defaults libgcc 4.8.5 2 defaults libgfortran 3.0.0 1 defaults libiconv 1.14 0 defaults libpng 1.6.27 0 defaults libsodium 1.0.10 0 defaults libtiff 4.0.6 3 defaults libxcb 1.12 1 defaults libxml2 2.9.4 0 defaults libxslt 1.1.29 0 defaults llvmlite 0.15.0 py35_0 defaults locket 0.2.0 py35_1 defaults lxml 3.7.2 py35_0 defaults markdown 2.6.8 py35_0 defaults markupsafe 0.23 py35_2 defaults matplotlib 2.0.0 np111py35_0 defaults mementos 1.2.2 mistune 0.7.3 py35_0 defaults mkl 2017.0.1 0 defaults mkl-service 1.1.2 py35_3 defaults mpldatacursor 0.6.2 0 BjornFJohansson mpmath 0.19 py35_1 defaults multipledispatch 0.4.9 py35_0 defaults nb_conda 2.0.0 py35_0 conda-forge nb_conda_kernels 2.0.0 py35_0 conda-forge nbconvert 5.1.1 py35_0 defaults nbformat 4.3.0 py35_0 defaults nbpresent 3.0.2 py35_1 conda-forge nbval 0.5 py35_0 BjornFJohansson networkx 1.11 py35_0 defaults nltk 3.2.2 py35_0 defaults nose 1.3.7 py35_1 defaults notebook 5.0.0 py35_0 defaults notedown 1.5.0 py35_0 BjornFJohansson numba 0.30.1 np111py35_0 defaults numexpr 2.6.1 np111py35_2 defaults numpy 1.11.3 py35_0 defaults numpydoc 0.6.0 py35_0 defaults odo 0.5.0 py35_1 defaults openpyxl 2.4.1 py35_0 defaults openssl 1.0.2k 0 defaults ordered-set 2.0.1 py35_0 conda-forge pandas 0.19.2 np111py35_1 defaults pandoc 1.19.1 0 BjornFJohansson pandoc-attributes 0.1.7 py35_0 BjornFJohansson pandocfilters 1.4.1 py35_0 conda-forge partd 0.3.7 py35_0 defaults patchelf 0.9 0 defaults path.py 10.0 py35_0 defaults pathlib2 2.2.0 py35_0 defaults patsy 0.4.1 py35_0 defaults pcre 8.39 1 defaults pdfkit 0.5.0 py35_0 bioconda pep8 1.7.0 py35_0 defaults percache 0.3.0 pexpect 4.2.1 py35_0 defaults pickleshare 0.7.4 py35_0 defaults pillow 4.0.0 py35_0 defaults pint 0.7.2 py35_0 conda-forge pip 9.0.1 py35_1 defaults pixman 0.34.0 0 defaults pkginfo 1.3.2 py35_0 defaults ply 3.9 py35_0 defaults poyo 0.3.0 py35_0 conda-forge prettytable 0.7.2 py35_0 conda-forge prompt_toolkit 1.0.9 py35_0 defaults psutil 5.0.1 py35_0 defaults ptyprocess 0.5.1 py35_0 defaults py 1.4.32 py35_0 defaults pyasn1 0.1.9 py35_0 defaults pycosat 0.6.1 py35_1 defaults pycparser 2.17 py35_0 defaults pycrypto 2.6.1 py35_4 defaults pycurl 7.43.0 py35_2 defaults pydna 2.0.0 pyflakes 1.5.0 py35_0 defaults pygments 2.1.3 py35_0 defaults pyinstaller 3.2.3 py35_0 acellera pylint 1.6.4 py35_1 defaults pyopenssl 16.2.0 py35_0 defaults pypandoc 1.4 py35_0 BjornFJohansson pyparsing 2.1.4 py35_0 defaults pypdf2 1.26.0 py35_1 conda-forge pyqt 5.6.0 py35_2 defaults pytables 3.3.0 np111py35_0 defaults pytest 3.0.5 py35_0 defaults pytest-cov 2.4.0 py35_0 conda-forge python 3.5.2 0 defaults python-dateutil 2.6.0 py35_0 defaults pytz 2016.10 py35_0 defaults pyyaml 3.12 py35_0 defaults pyzmq 16.0.2 py35_0 defaults qt 5.6.2 3 defaults qtawesome 0.4.3 py35_0 defaults qtconsole 4.3.0 py35_0 defaults qtpy 1.2.1 py35_0 defaults readline 6.2 2 defaults redis 3.2.0 0 defaults redis-py 2.10.5 py35_0 defaults reportlab 3.3.0 py35_0 defaults requests 2.12.4 py35_0 defaults requests-toolbelt 0.7.0 py35_0 conda-forge rope 0.9.4 py35_1 defaults ruamel_yaml 0.11.7 py35_0 defaults runipy 0.1.5 py35_0 defaults scikit-image 0.12.3 np111py35_1 defaults scikit-learn 0.18.1 np111py35_1 defaults scipy 0.18.1 np111py35_1 defaults seaborn 0.7.1 py35_0 defaults setproctitle 1.1.10 py35_0 conda-forge setuptools 27.2.0 py35_0 defaults sh 1.11 py35_0 defaults simplegeneric 0.8.1 py35_1 defaults simplejson 3.10.0 py35_0 defaults singledispatch 3.4.0.3 py35_0 defaults sip 4.18 py35_0 defaults six 1.10.0 six 1.10.0 py35_0 defaults snowballstemmer 1.2.1 py35_0 defaults sockjs-tornado 1.0.3 py35_0 defaults sphinx 1.5.1 py35_0 defaults sphinx_rtd_theme 0.1.9 py35_0 defaults spyder 3.1.4 py35_0 defaults sqlalchemy 1.1.5 py35_0 defaults sqlite 3.13.0 0 defaults statsmodels 0.6.1 np111py35_1 defaults sympy 1.0 py35_0 defaults termcolor 1.1.0 py35_1 conda-forge terminado 0.6 py35_0 defaults testpath 0.3 py35_0 conda-forge tk 8.5.18 0 defaults toolz 0.8.2 py35_0 defaults tornado 4.4.2 py35_0 defaults tqdm 4.11.2 py35_0 defaults traitlets 4.3.2 py35_0 defaults twine 1.8.1 py35_1 conda-forge typing 3.5.2.2 unicodecsv 0.14.1 py35_0 defaults unidecode 0.04.20 py35_0 defaults urllib3 1.16 py35_1 conda-forge urllib3 1.18 versioneer 0.18 py35_0 conda-forge wcwidth 0.1.7 py35_0 defaults werkzeug 0.11.15 py35_0 defaults wheel 0.29.0 py35_0 defaults whichcraft 0.4.0 py35_0 conda-forge widgetsnbextension 2.0.0 py35_0 defaults wkhtmltopdf 0.12.3 0 bioconda wrapt 1.10.8 py35_0 defaults xlrd 1.0.0 py35_0 defaults xlsxwriter 0.9.6 py35_0 defaults xlwt 1.2.0 py35_0 defaults xz 5.2.2 1 defaults yaml 0.1.6 0 defaults zeromq 4.1.5 0 defaults zlib 1.2.8 3 defaults ```
ccordoba12 commented 7 years ago

@BjornFJohansson, what if you create a conda environment with Spyder, free of any conda-forge package?

ccordoba12 commented 7 years ago

Ups, sorry @BjornFJohansson, it seems you don't have any problem.

FuZhiyu commented 7 years ago

I had used VSC for a while until I needed to do some exploratory work and changed back to Spyder. I have done nothing but reopen it, but the code completion miraculously comes back! I swear I have reopened and even reinstalled it for plenty of times yesterday, and have done nothing related to spyder even since I gave up.

But it works now. O.o

ccordoba12 commented 7 years ago

@FuZhiyu, I think that's because you updated Jedi and restarted Spyder after that.

nbroers commented 7 years ago

Please let me know if I can help in any way? I have the same issue on my environment. Details in Bug #4587 (marked as duplicate)

ccordoba12 commented 7 years ago

We don't know why this is happening. Our recommendation (for now) is to use Anaconda, which doesn't have this problem.

bharathvn commented 7 years ago

I am running Anaconda on Mac Sierra. I am facing this issue.

PJussel commented 7 years ago

Facing same issue, freshly installed Annaconda 4.4.0, python settings reset, running on Win7 64bit.

PS: after restarting spyder (2-3 times) autocomplete and help started to work in editor...

nbud commented 7 years ago

Same issue with the editor. import num<TAB> has no effect in the editor but works in the IPython console. Ctrl+I works in the console but not in the editor.

Windows 7 64 bits, Python 3.6.1, Spyder 3.1.4, Anaconda 4.4.0 custom (ipython 6.1.0 instead of 5.3.0)

Optional dependencies for Spyder:

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.12.1 (OK)
pandas >=0.13.1  :  0.20.1 (OK)
pep8 >=0.6       :  1.7.0 (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)
ceaza commented 7 years ago

Not working on Anaconda either in the project view.

depkchowdary commented 7 years ago

Not working in 3.1.6 in Anaconda environment

Dependencies : 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.12.1 (OK) pandas >=0.13.1 : 0.20.1 (OK) pep8 >=0.6 : 1.7.0 (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)

Juffled commented 7 years ago

Works fine for me when the editor window is 'docked' within the main window, but fails when it is on its own/'pop-out' whatever you want to call it

gleefeng commented 7 years ago

when I re-downgraded Jedi to 0.9.0 and re-downgraded the Spyder to 3.1.0, it worked again, win7 x64 anconda4.4.0

arman00 commented 7 years ago

After some extensive testing with various versions of Spyder, WinPython, Anaconda, python and Jedi (testing on Win7 x64), I think I found where the problem is: It happens only because of opening/creating any "Spyder project" with Spyder versions >=3.1.4 . I hope that below notes will be helpful in fixing the bug.

This happens the same in Anaconda (tested 4.4.0, 4.3.0) and WinPython (tested with latest stable and beta versions), Python 3.5 & 3.6 and jedi versions.

***For Spyder version >= 3.1.4 It happens only when editing files which are within in a Spyder project or when/after a Spyder project is opened (it doesn't depend on the version of the jedi). I observed below cases:

  1. Editing a script (saved in a file or not) while no project is opened: works fine
  2. Editing a script (saved in a file or not) which is not included in a project while a project is opened: does not work
  3. Editing a script which is included in a project while a project is opened: does not work
  4. Editing a script (saved in a file or not) which is not included in a project and there is no project opened, but the script is edited after a project was closed: does not work (I also tried to restart a new kernel, never works if a Spyder project was opened at least once before, even though there is currently no project opened in Spyder)

***For Spyder version 3.1.3 (probably with the lower versions as well), I haven't observed this problem. Note that I tested both Jedi 0.9.0 and 0.10.2, and this problem did not happen, although Spyder warns that version 0.10.2 is not okay (NOK).

I have also noticed some slow down for several seconds (maybe 5 secs) when "import module"+Tab is pressed for the first time, but after the first attempt, the successive attempts work fast. I suppose jedi puts it into a cache or something like this. This slow down doesn't happen all the time though, and maybe related to the observations reported by @stonebig

ccordoba12 commented 7 years ago

@arman00, thanks a lot for your thorough investigation and for narrowing down the problem.

@dalthviz, please start to work on this problem to see if you can find its root cause. I think it could have been caused by PR #4263.

arman00 commented 7 years ago

I am not sure if this fix has already been included in the 3.2 release, but I have noticed a case where it doesn't work with 3.2 and another case where it works.

In a file opened in the editor where I import both a standard Python module and another script as a module from a different path

Thanks,

laikh commented 7 years ago

I working with anaconda3 and Spyder 3.2 on WindowsX64 and have exactly all the Problems described by @arman00 above. Autocompletition seemed to work fine in the previous Version of Spyder.

IPython >=4.0 : 5.1.0 (OK) cython >=0.21 : 0.25.2 (OK) jedi >=0.9.0 : 0.10.2 (OK) nbconvert >=4.0 : 4.2.0 (OK) numpy >=1.7 : 1.11.3 (OK) pandas >=0.13.1 : 0.19.2 (OK) pycodestyle >=2.3: 2.3.1 (OK) pyflakes >=0.6.0 : 1.5.0 (OK) pygments >=2.0 : 2.1.3 (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.1 (OK) sympy >=0.7.3 : 1.0 (OK)

ccordoba12 commented 7 years ago

@dalthviz is working to fix this in 3.2.1. Thanks for your patience.

ccordoba12 commented 7 years ago

Those of you who are affect by this problem, please help us to test PR #4783. We'd really appreciate your help.

arman00 commented 7 years ago

@ccordoba12 I would like to test it. What is the most practical way of installing with the latest updates for the testing? Is there a pip command to install the latest development version?

dalthviz commented 7 years ago

Hi @arman00 if you are familiar with git you can git-clone this repo and checkout the branch fixes_issue_4410. To run Spyder you can use python bootstrap.py or if there is a Spyder instance already running you can use python bootstrap.py -- --new-instance from cmd or a terminal in the root directory of the cloned repo. Should by something like:

git clone https://github.com/dalthviz/spyder.git
cd spyder
git checkout fixes_issue_4410
python bootstrap.py

Also doing this you can do git pull to get the changes that are being done.

Another way is to replace the files changed in the installed Spyder you have and restart Spyder, although you will have to replace them every time a change is done.

Something important is that you need to restart Spyder (close and open again) to see the changes running (after doing git pull or the manual replace of the files).

CoderCoderCoder commented 6 years ago

The help functionality (Cmd+I) in editor still doesn't work, even in 3.2.4. Any chance it will be fixed finally? Have to revert each time to 3.1.3, last working version for me. MacOS High Sierra

IPython >=4.0 : 5.3.0 (OK) cython >=0.21 : 0.25.2 (OK) jedi >=0.9.0 : 0.9.0 (OK) nbconvert >=4.0 : 5.1.1 (OK) numpy >=1.7 : 1.13.3 (OK) pandas >=0.13.1 : 0.20.3 (OK) psutil >=0.3 : 5.2.2 (OK) pycodestyle >=2.3: 2.3.1 (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 (OK) sphinx >=0.6.6 : 1.6.5 (OK) sympy >=0.7.3 : 1.0 (OK)

nerdykamil commented 6 years ago

Facing same issue as stated by @CoderCoderCoder, using ubuntu 16.04, spyder 3.2.4, anaconda 5.0.1

halidziya commented 6 years ago

After setting PYTHONPATH environment variable it started working

CoderCoderCoder commented 6 years ago

@halidziya Can you describe step-by-step please what exactly you did to solve this issue? Thanks!

halidziya commented 6 years ago

Windows : Right click computer -> Properties -> Advanced system settings -> Environment Variables -> New Then add PYTHONPATH variable with value of your python location (i.e C:\Python). I added to both user and system variables to make sure it is available in both env.

--- Update ---- It was broken again (somehow) on my laptop . It seems working after updating to Spyder 3.2.5

pip install -U spyder

CoderCoderCoder commented 6 years ago

@halidziya I tried out your solution - it doesn't work on my Mac. Set both $PATH and $PYTHONPATH to anaconda/bin - it doesn't help to fix the issue. Back to 3.1.3...

@ccordoba12 Carlos, is there any chance to get this issue fixed in the next version?... It prevents me and other users who have the same problem from using all new cool stuff introduced in the last versions, including Jupyter notebooks support. Many thanks!!

ccordoba12 commented 6 years ago

@CoderCoderCoder, we don't know why this is happening. There's an open issue about this: issue #5782. Please follow my advice there or post your conda list to try to help you.

vladostan commented 6 years ago

Had the same issue, removing enum34 helped. But still can't 'Go to Definition' (Ctrl+G)

ratnadeepb commented 6 years ago

I have been experiencing the same issue with Ubuntu 16.04 on VirtualBox VM. However, I have never faced this on my native Windows 10.

kepy97 commented 6 years ago

I just reinstalled anaconda and auto completion working now.

Steps that I followed:

1> Uninstall Anaconda from control panel 2> Restart Computer 3> Download and install anconda from [https://www.anaconda.com/download/#windows] 4> Restart again before it you start anaconda. 5> done.

Dependencies in spyder - 3.2.4 (python 3.6)

IPython >=4.0 : 6.1.0 (OK) cython >=0.21 : 0.26.1 (OK) jedi >=0.9.0 : 0.10.2 (OK) nbconvert >=4.0 : 5.3.1 (OK) numpy >=1.7 : 1.13.3 (OK) pandas >=0.13.1 : 0.20.3 (OK) pycodestyle >=2.3: 2.3.1 (OK) pyflakes >=0.6.0 : 1.6.0 (OK) pygments >=2.0 : 2.2.0 (OK) pylint >=0.25 : 1.7.4 (OK) qtconsole >=4.2.0: 4.3.1 (OK) rope >=0.9.4 : 0.10.5 (OK) sphinx >=0.6.6 : 1.6.3 (OK) sympy >=0.7.3 : 1.1.1 (OK)

nosyarlin commented 6 years ago

I was facing the same problem after installing some packages (tensorflow and keras). My python was originally 3.6.2 and spyder 3.2.6. I fixed the problem by updating all my packages, then downgrade python to 3.5.4, and reinstalling spyder. I have no idea which part of the process fixed it. I hope this helps someone.

ayguno commented 6 years ago

@nosyarlin I am struggling with the same issue in a Sierra 10.12.1 with anaconda . I was about to give up until I noticed your recent post. It also happened to me right after installing tensorflow and keras, so we might be experiencing the same issue. When I tried to downgrade python to 3.5.6 using the command:

conda install python=3.5.4

I got the following error:

Solving environment: failed

UnsatisfiableError: The following specifications were found to be in conflict:
  - pytables -> numexpr -> numpy=1.12 -> python=3.6
  - python=3.5.4
Use "conda info <package>" to see the dependencies for each package.

I have trouble in numpy this time and I can not downgrade it further...Would you mind describing how you overcome this problem eventually?

nosyarlin commented 6 years ago

I didn't face that problem. pytables 3.4.2 py35hda701c8_2 numpy 1.13.3 py35hfd7066c_0 Both my pytables and numpy use python 3.5. You can try uninstalling those packages first, install python 3.5, then reinstall pytables? Sorry that i can't provide much help!

stevewyl commented 6 years ago

Had the same issue, removing enum34 still cannot fix this problem. I installed the latest Python 3.6.4.

urbandw commented 6 years ago

FWIW, downgrading from spyder 3.2.4 to spyder 3.1.4 worked for me.

MacOS Sierra python 3.6.4 ipython 6.2.1 Qt 5.6.2 PyQt 5.6.0