Since I mentioned your plugin today, and had a few spare minutes, I finally got it working with my python2.7 installation (I couldn't install python-lsp-server as you had suggested in October, but I found that I could install python-language-server with pip2 and got pyls that way... and once I saw that the config file language had changed from JSON to TOML, I was able to get either the IO or the TCP pointed at the pyls.exe and working. 🎉
As I was trying some features, I was surprised to see when looking in my startup.py where I import some of my scripts to automatically run, on the ones that were correctly defined with a docstring at the beginning, hovering correctly worked... so it was correctly finding the right module in the search path, which highly impressed me!
But then I tried to NppLspClient > Goto Definition on the same one, and it popped up the error:
I tried on a standard library (like import os) and it correctly went to the definition (which told me the feature itself is functional). But apparently the ++ being translated to %2B%2B messed up whatever underlying open function is being used.
Looking at the log, the only mentions of %2B were here:
Thank you, yes, I can confirm and reproduce this problem.
A path must be encoded as URI, which must be en- and decoded accordingly.
The problem will be fixed with the next version.
Since I mentioned your plugin today, and had a few spare minutes, I finally got it working with my python2.7 installation (I couldn't install python-lsp-server as you had suggested in October, but I found that I could install python-language-server with pip2 and got pyls that way... and once I saw that the config file language had changed from JSON to TOML, I was able to get either the IO or the TCP pointed at the pyls.exe and working. 🎉
As I was trying some features, I was surprised to see when looking in my
startup.py
where I import some of my scripts to automatically run, on the ones that were correctly defined with a docstring at the beginning, hovering correctly worked... so it was correctly finding the right module in the search path, which highly impressed me!But then I tried to NppLspClient > Goto Definition on the same one, and it popped up the error:
I tried on a standard library (like
import os
) and it correctly went to the definition (which told me the feature itself is functional). But apparently the++
being translated to%2B%2B
messed up whatever underlying open function is being used.Looking at the log, the only mentions of
%2B
were here: