Open awood45 opened 3 years ago
I apologize if I am stating the obvious, but I think you need to make sure your config is setup. You don't have anything installed in your elpy-config. Maybe Flymake depends on these? This should get prompted when you create/open a python file. Not sure why it's not...
But I'm still Elpy/Emacs noob and your config file makes me think you know what you're doing. So sorry if my comment isn't all that helpful. :/
It's not outside the realm of possibility that I've misconfigured something, though I don't think that's the cause here:
Sorry, I should have elaborated on what I meant by "prompted". IIRC, when I saved a python file (or when I called M-x elpy-config), the RPC process began installing all the necessary sub packages (as listed in elpy-config), and everything gets installed. Sadly, I can't remember if this happened when I saved a python file or when I called elpy-config
This is my elpy-config
result.
Elpy..............: 1.35.0
Virtualenv........: env (c:/Users/user/Documents/env/)
Interactive Python: python 3.8.2 (c:/Users/user/Scripts/python.exe)
RPC virtualenv....: rpc-venv (c:/Users/user/.emacs.d/elpy/rpc-venv)
Python...........: c:/WINDOWS/py.exe 3.9.0 (c:/WINDOWS/py.exe)
Jedi.............: 0.17.2
Rope.............: 0.18.0
Autopep8.........: 1.5.4
Yapf.............: 0.30.0
Black............: 20.8b1
Syntax checker....: flake8.exe (c:/Users/user/AppData/Local/Programs/Python/Python39/Scripts/flake8.exe)```
Summary
Whenever I open a new Python file, I get the following error:
The
black
part doesn't seem to matter, if I disable'(elpy-syntax-check-command "black")
all other syntax checkers will fail with the exact same message.The
*Messages*
buffer also shows the following messages preceding this failure:Steps to reproduce
In my case, any time I open up a Python file. I have another laptop where this doesn't seem to happen, including on the same projects, but I haven't quite been able to divine the material difference yet.
My configuration
OS
OSX
Result of
(elpy-config)
(I will note that turning on a virtualenv does nothing for this error.)
Elpy configuration in my init.el
I have a whole file structure, but here are the relevant parts - happy to dive in deeper if there may be something else relevant.