Closed jrast closed 7 years ago
@dalthviz, please take a look at this one. Notice that the OP has Jedi 0.10.2 installed.
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.
got this too, downgraded to 0.9.0 from 0.10.0 and it came back.
I got the same issue. Changing jedi version didn't work for me. Downgrading spyder from 3.1 to 3.0 worked for me.
could it be a timeout issue ? on a too slowed computer, jedi abort itself ?
Is this only happening on Windows for you guys?
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
on my old pc, spyder3.2.0dev2017-05-11:
<Tab>
to launch completion before all processes have calmed down (50 seconds after launching Spyder), no completion will happen.in the past, hot restart were quick,
spyder --reset
)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.
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.
Packages for pip are also all up to date.
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.
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
I run on ubuntu like this and it seems to work
@BjornFJohansson, what if you create a conda environment with Spyder, free of any conda-forge package?
Ups, sorry @BjornFJohansson, it seems you don't have any problem.
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
@FuZhiyu, I think that's because you updated Jedi and restarted Spyder after that.
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)
We don't know why this is happening. Our recommendation (for now) is to use Anaconda, which doesn't have this problem.
I am running Anaconda on Mac Sierra. I am facing this issue.
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...
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)
Not working on Anaconda either in the project view.
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)
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
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
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:
***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
@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.
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,
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)
@dalthviz is working to fix this in 3.2.1. Thanks for your patience.
Those of you who are affect by this problem, please help us to test PR #4783. We'd really appreciate your help.
@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?
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).
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)
Facing same issue as stated by @CoderCoderCoder, using ubuntu 16.04, spyder 3.2.4, anaconda 5.0.1
After setting PYTHONPATH environment variable it started working
@halidziya Can you describe step-by-step please what exactly you did to solve this issue? Thanks!
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
@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!!
@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.
Had the same issue, removing enum34 helped. But still can't 'Go to Definition' (Ctrl+G)
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.
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)
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.
@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?
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!
Had the same issue, removing enum34 still cannot fix this problem. I installed the latest Python 3.6.4.
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
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)