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

Spyder editor keeps crashing #6085

Closed
xiaoyuejin opened this issue Dec 29, 2017 · 10 comments
Closed

Spyder editor keeps crashing #6085

xiaoyuejin opened this issue Dec 29, 2017 · 10 comments

Comments

@xiaoyuejin
Copy link

xiaoyuejin commented Dec 29, 2017

Description

What steps will reproduce the problem?

  1. Updated to spyder 3.2.4
  2. In the editor, type in, for example, "numpy.", OR
  3. type in "(" and autocomplete to "()"

Note: I have
parso 0.1.0
jedi 0.10.2
But the problem remains.

What is the expected output? What do you see instead?
Popup window: [Spyder has encountered a problem]

Please provide any additional information below

File "c:\python27\lib\site-packages\spyder\utils\introspection\manager.py", line 220, in get_completions
info = self._get_code_info('completions', automatic=automatic)
File "c:\python27\lib\site-packages\spyder\utils\introspection\manager.py", line 216, in _get_code_info
**kwargs)
File "c:\python27\lib\site-packages\spyder\utils\introspection\utils.py", line 75, in init
self.get_info()
File "c:\python27\lib\site-packages\spyder\utils\introspection\utils.py", line 87, in get_info
lexer = find_lexer_for_filename(self.filename)
File "c:\python27\lib\site-packages\spyder\utils\introspection\utils.py", line 180, in find_lexer_for_filename
lexer = get_lexer_for_filename(filename)
File "c:\python27\lib\site-packages\pygments\lexers_init
.py", line 203, in get_lexer_for_filename
res = find_lexer_class_for_filename(fn, code)
File "c:\python27\lib\site-packages\pygments\lexers_init
.py", line 168, in find_lexer_class_for_filename
for cls in find_plugin_lexers():
File "c:\python27\lib\site-packages\pygments\plugin.py", line 53, in find_plugin_lexers
yield entrypoint.load()
File "c:\python27\lib\site-packages\pkg_resources_init
.py", line 2354, in load

@ccordoba12
Copy link
Member

The error is not complete. Please copy it from our error dialog and paste it in full here.

@CAM-Gerlach
Copy link
Member

It still looks very much like the parso error; e.g. #5673 , the part of the traceback we can see fits the signature exactly. Most importantly, what does the last line of the error message say?

Also, given it looks like you are using pip, it could be some arcane issue with that. Due to the frequency of such problems, we can only recommend that you use the Anaconda distribution instead, though you're welcome to try to get it on your own. Also, you can try updating both parso and jedi to their latest versions, which should now work well together.

Finally, if we don't hear from you in one week (7 days), we'll have to close this error report. Best of luck!

@xiaoyuejin xiaoyuejin changed the title Spyder editor keeps crushing Spyder editor keeps crashing Dec 29, 2017
@xiaoyuejin
Copy link
Author

xiaoyuejin commented Dec 29, 2017

I am using pythonxy 2.7.10, i.e. Python 2.7.10.

I had upgraded both parso and jedi to the latest version, then had this problem. I was digging in github and found that sometimes the latest versions of parso and jedi cause problems. That's why I downgraded both them. But the problem remains.

And, my spyder does NOT show error message in full. The pop-up window only says "Spyder has encountered a problem", then "submit to GITHUB" or "OK". Where can I load/find the full error message?

untitled

@ccordoba12
Copy link
Member

Please press the button that says Show details (or something like that) and copy the text that appears below.

@CAM-Gerlach
Copy link
Member

CAM-Gerlach commented Dec 29, 2017

I had upgraded both parso and jedi to the latest version, then had this problem.

What versions, precisely?

Where can I load/find the full error message?

You can also try the Spyder internal console. View > Panes > Internal Console.

Not sure why the full error message isn't getting copied...I've seen this very frequently in people's posts, but I've never understood why since I'm not sure at what step it happens, and it's never happened to me.

@xiaoyuejin
Copy link
Author

I just uploaded a screenshot of the popup window. There is no place where I can click for "more details"...

untitled

@xiaoyuejin
Copy link
Author

But I found the internal console now. Here is the full error:

Traceback (most recent call last):
File "c:\python27\lib\site-packages\spyder\utils\introspection\manager.py", line 220, in get_completions
info = self.get_code_info('completions', automatic=automatic)
File "c:\python27\lib\site-packages\spyder\utils\introspection\manager.py", line 216, in get_code_info
**kwargs)
File "c:\python27\lib\site-packages\spyder\utils\introspection\utils.py", line 75, in init
self.get_info()
File "c:\python27\lib\site-packages\spyder\utils\introspection\utils.py", line 87, in get_info
lexer = find_lexer_for_filename(self.filename)
File "c:\python27\lib\site-packages\spyder\utils\introspection\utils.py", line 180, in find_lexer_for_filename
lexer = get_lexer_for_filename(filename)
File "c:\python27\lib\site-packages\pygments\lexers_init
.py", line 203, in get_lexer_for_filename
res = find_lexer_class_for_filename(fn, code)
File "c:\python27\lib\site-packages\pygments\lexers_init
.py", line 168, in find_lexer_class_for_filename
for cls in find_plugin_lexers():
File "c:\python27\lib\site-packages\pygments\plugin.py", line 53, in find_plugin_lexers
yield entrypoint.load()
File "c:\python27\lib\site-packages\pkg_resources_init
.py", line 2354, in load
self.require(*args, **kwargs)
File "c:\python27\lib\site-packages\pkg_resources_init
.py", line 2371, in require
items = working_set.resolve(reqs, env, installer)
File "c:\python27\lib\site-packages\pkg_resources_init
.py", line 844, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (setuptools 18.0.1 (c:\python27\lib\site-packages), Requirement.parse('setuptools>=18.5'))

I will try to upgrade setuptools now and will report back. Thanks guys!

@xiaoyuejin
Copy link
Author

No, I can't see the full thing when I submit to github... There is only a popup window but no text panel in it.

@ccordoba12
Copy link
Member

Please try to use a more recent version of, well, everything, Python, setuptools, PyQt. etc.

Closing because this is why we don't give support to installations other than Anaconda.

@CAM-Gerlach
Copy link
Member

Closing because this is why we don't give support to installations other than Anaconda.

Yup...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants