Went down the rabbit hole of seeing if I could setup #elpy for #emacs on #Windows. Mixed results. Of course it installs, however it doesn't seem capable of finding anything. I have all the Python dependencies installed, and C:/Python311/Scripts and C:/Python311 are the top two paths. It finds Python just dandy. Yet it still cannot find autopep8, jedi, and black. It DID find flake... right where autopep8 and black are located. I have no idea what it's trying to accomplish nor how to help it along.
It is unfortunate that #elpy is unmaintained.
The closest match to elpy using the #LanguageServerProtocol was initially written by Palantir which makes me feel dirty. But so does all the warnings generated by loading elpy into #emacs 28.
https://github.com/python-lsp/python-lsp-server/blob/develop/LICENSE#L3
#elpy #languageserverprotocol #emacs
I've just completed the 6th day of the course #100daysofcode
I'm loving #python even more! And btw, I'm using #emacs to follow the course!
Have to say that the combination of #yasnippets and #elpy is fantastic!
#elpy #yasnippets #emacs #python #100daysofcode
Elpy is a
"Emacs Python Development Environment".
Sad to know #elpy is losing steam... It's also removed from debian unstable.
Maintainer needed (at least for a while...) · Issue #1884 · jorgenschaefer/elpy · GitHub