Open fm4d opened 8 years ago
Hello, and thanks for the report! This is interesting, I have only seen something like it when Elpy defaults to the dabbrev backend instead of using jedi/rope – do you have reproduction steps that show this behavior?
Well there are not really any steps to reproduce, I just installed Elpy and recommended python packages from elpy documentation. I chose jedi over rope and elpy-config seems to be fine.
Virtualenv........: None
RPC Python........: 3.5.1 (/usr/bin/python)
Interactive Python: ipython (/usr/bin/ipython)
Emacs.............: 25.0.92.1
Elpy..............: 1.11.0
Jedi..............: 0.9.0
Rope..............: Not found (0.10.3 available)
Importmagic.......: 0.1.3
Autopep8..........: 1.2.2
Yapf..............: 0.6.2
Syntax checker....: pyflakes (/usr/bin/pyflakes)
Completion as such seems to be ok, I am not really sure how to check what backend is Elpy using.
Do the completions have annotations, like "module" or "function", on the right side?
Yes they do.
Hrm. That means they do indeed come from the backend, jedi in your case. The other completion sources for company do not add such annotations. I just tried again locally, and I do not get differently-cased completions. I'm at a loss here. Maybe Jedi can get into some form of confusion about this?
Names starting with uppercase letter are beign listed by company even when starting with lowercase letter, for example
ValueError
is also listed asvalueError
if you start writingval
and completed intovalueError
.