jorgenschaefer / elpy

Emacs Python Development Environment
GNU General Public License v3.0
1.9k stars 262 forks source link

rope: TypeError: cannot concatenate 'str' and 'NoneType' objects #826

Closed jmercouris closed 8 years ago

jmercouris commented 8 years ago

Really Doesn't like my piece of code, crashes on it every time when I'm writing

journalfile.write(next ...)

debug.txt

jorgenschaefer commented 8 years ago

Hello, and thanks for the report! I'm afraid that debug.txt link is not leading anywhere – what output do you get from Elpy when it crashes? :-)

jmercouris commented 8 years ago

Hey, I'm sorry that's all the details I could get, it would just open up in a new buffer and had that output, is there some log that I can check? If I recreate the crash, what should I do?

On Fri, Mar 11, 2016 at 10:08 AM, Jorgen Schäfer notifications@github.com wrote:

Hello, and thanks for the report! I'm afraid that debug.txt link is not leading anywhere – what output do you get from Elpy when it crashes? :-)

— Reply to this email directly or view it on GitHub https://github.com/jorgenschaefer/elpy/issues/826#issuecomment-195430329 .

jorgenschaefer commented 8 years ago

Usually, when Elpy encounters a problem, it pops up a debug window with more information.

What exactly do you mean with "crashes"? Does your Emacs actually crash, as in, terminate?

jmercouris commented 8 years ago

Emacs did not terminate. What I did when it crashed was open up a scratch buffer, copy all the text from the debug window and yank it into the scratch buffer, that is what I attached. Is there another log I should look for, or a different way to pull the data?

On Sat, Mar 12, 2016 at 9:20 AM, Jorgen Schäfer notifications@github.com wrote:

Usually, when Elpy encounters a problem, it pops up a debug window with more information.

What exactly do you mean with "crashes"? Does your Emacs actually crash, as in, terminate?

— Reply to this email directly or view it on GitHub https://github.com/jorgenschaefer/elpy/issues/826#issuecomment-195759758 .

jorgenschaefer commented 8 years ago

Ah, there we go … when I first tried to download that debug.txt, the link was broken.

Traceback (most recent call last):
  File "/Users/jmercouris/.emacs.d/elpa/elpy-20151101.401/elpy/ropebackend.py", 
line 100, in call_rope
    **kwargs)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.
7/site-packages/rope/contrib/codeassist.py", line 101, in get_calltip
    return PyDocExtractor().get_calltip(pyobject, ignore_unknown, remove_self)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.
7/site-packages/rope/contrib/codeassist.py", line 569, in get_calltip
    result = self._get_function_signature(pyobject, add_module=True)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.
7/site-packages/rope/contrib/codeassist.py", line 619, in _get_function_signatur
e
    return '%s(%s)' % (location + pyfunction.get_name(),
TypeError: cannot concatenate 'str' and 'NoneType' objects

This is a bug in Rope I'm afraid. As a workaround, you can either set elpy-disable-backend-error-display to t to avoid this display, or try using Jedi instead of Rope. I'll report this upstream.

Thanks for the report!

jorgenschaefer commented 8 years ago

Actually, looks like this is the same error as #805 – I'll close this issue so we can keep the discussion in one spot. In any case, it was good to have this report. Thank you!

jmercouris commented 8 years ago

No problem! Good luck!

On Mar 13, 2016, at 01:48, Jorgen Schäfer notifications@github.com wrote:

Actually, looks like this is the same error as #805 – I'll close this issue so we can keep the discussion in one spot. In any case, it was good to have this report. Thank you!

— Reply to this email directly or view it on GitHub.