search

jorgenschaefer / elpy

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

get "elpy-rpc ready^M" in the *elpy-rpc* buffer #116

Closed alphaho closed 11 years ago

alphaho commented 11 years ago

Get error message:

"Unknown output from Python elpy-rpc"

When elpy try to elpy-rpc-open.

Because in the elpy-rpc buffer, it gets

elpy-rpc ready^M

rather than

elpy-rpc ready

Running on Windows 7 with Emacs 24.3.1

jorgenschaefer commented 11 years ago

Thanks for the report. I sadly lack a Windows system to reproduce this, so this will be a bit tricky to fix …

What's the value of default-process-coding-system for you?

Does the same problem happen when you don't use your .emacs?

alphaho commented 11 years ago

Thank for pointing out. I have checked my default-processs-coding-system, and it is (utf-8-unix . utf-8-unix). And while I start emacs without my settings, the elpy can run without coding problems with default-process-coding-system set to (undecided-dos . undecided-unix). I reconfigure my .emacs like so, then everything works well. :-D

jorgenschaefer commented 11 years ago

Glad it works now :-)

Do you know why default-process-coding-system was set to (utf-8-unix . utf-8-unix) at your end? Is this normal for Emacs under Windows? If so, elpy might need to work around that.

theanalyst commented 11 years ago

The default-process-coding-system in native windows emacs should be (undecided-dos . undecided-unix) (Not sure in cygwinized builds). At least this is the value for me (with both emacs -Q\ or with my init file) for emacs since 23 onwards. Other than that I have observed that process-coding-system-alist sets up defaults for PuTTY and cmd as 

(("[pP][lL][iI][nN][kK]" undecided-dos . undecided-dos)
 ("[cC][mM][dD][pP][rR][oO][xX][yY]" undecided-dos . undecided-dos))
jorgenschaefer commented 11 years ago

That should be correct, then. Thanks!

I'll assume this was a misconfiguration on the user side somehow. If that is wrong and elpy should change behavior here somehow, please do not hesitate to reopen the issue.

Thanks for the report!

alphaho commented 11 years ago

This was configured by myself, so no need to work around for this issue. Thanks for your help!

hrehfeld commented 10 years ago

My elpy installation returns the version number, which breaks elpy-mode inside emacs with the same error as above:

  $ python -m elpy.__main__
  elpy-rpc ready (1.2.1)

Elpy installed with package.el:

elpy is an installed package.

 Status: Installed in `/home/hrehfeld/.emacs.d/el-get/package/elpa/elpy-1.0/'.
Version: 1.0

Requires: auto-complete-1.4, fuzzy-0.1, yasnippet-0.8, virtualenv-1.2, highlight-indentation-0.5.0, find-file-in-project-3.2, idomenu-0.1, nose-0.1.1, iedit-0.97 Summary: Emacs Lisp Python Environment

jorgenschaefer commented 10 years ago

@hrehfeld, the Python package of elpy you installed is version 1.2.1, while the Emacs Lisp package you installed is version 1.0. You should upgrade the lisp package. (Starting with version 1.2, elpy will give a much more readable error in these cases.)