Replies: 2 comments 5 replies
-
|
null-ls is not getting the old Python path from anywhere - that error comes from the commands themselves. Can you successfully run |
Beta Was this translation helpful? Give feedback.
-
|
Yes. This was run within NeoVim 0.8 terminal: C:\rnl\code>pylint c:\rnl\code\scratch.py Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00) C:\rnl\code When I do run the command - I do not see any other message being returned i.e. I do not see the old path mentioned. If I look in Mason->pylint it has pyvenv.cfg but that is pointing correctly to c:\python310 |
Beta Was this translation helpful? Give feedback.
-
|
null-ls' logic here is simple: look at the If you are convinced that this is an issue with null-ls itself and can put together a reproduction that does not depend on your local environment, please open an issue. |
Beta Was this translation helpful? Give feedback.
-
|
Windows environment variables: So - in theory Null-ls is going to the right location - that is where the python.exe is located. Given what you said Null-ls is doing then it should have executed the right python executable - how and from where did it get the wrong path? |
Beta Was this translation helpful? Give feedback.
-
|
To be clear, judging from your log output null-ls is not getting the "wrong path" here. It is correctly picking up the path to If I had to guess what's going wrong here, I would guess it's Mason, since that will modify your |
Beta Was this translation helpful? Give feedback.
-
|
OK thanks |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
The old Python310 path was c:\rnl\python310 and the new path is c:\python310. In short, it was uninstalled and then reinstalled to a new location by a package manager and I have then tried to update NeoVim and plugins to use the new location...
Null-ls still points or tries to use the old location:
[TRACE 09/10/2022 19:27:42] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:203: error output: No Python at '"c:\rnl\python310\python.exe' (NB dangling " in string) It is not clear where Null-ls is getting the (old) python path from.
Null-ls has been uninstalled and reinstalled via packer and manually but that has not helped. Null-ls is working generally within a python file as black and flake8, mypy, pylint do work on that file and so I do get formatting and diagnostics.
Opening a command prompt outside and inside NeoVim and typing python -V or pip list both work as expected. System/user environment variable points to new python location and old path has been removed. NeoVim checkhealth also finds python "OK" and g:python3_host_prog is set to the virtual environment. So, I can run python HelloWorld.py from within NeoVim without issue.
How do I remove this incorrect path and how can I set Null-ls to use the updated Python310 location?
Debug Log does not seem to provide any insight:
[TRACE 10/10/2022 08:32:31] ...te\pack\packer\start\null-ls.nvim/lua/null-ls/client.lua:110: starting null-ls client
[TRACE 10/10/2022 08:32:31] ...\site\pack\packer\start\null-ls.nvim/lua/null-ls/rpc.lua:123: received LSP request for method initialize
[TRACE 10/10/2022 08:32:31] ...\site\pack\packer\start\null-ls.nvim/lua/null-ls/rpc.lua:148: received LSP notification for method initialized
[TRACE 10/10/2022 08:32:31] ...\site\pack\packer\start\null-ls.nvim/lua/null-ls/rpc.lua:148: received LSP notification for method textDocument/didOpen
[TRACE 10/10/2022 08:32:31] ...ack\packer\start\null-ls.nvim/lua/null-ls/generators.lua:21: running generators for method NULL_LS_DIAGNOSTICS_ON_OPEN
[DEBUG 10/10/2022 08:32:31] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:319: spawning command "pylint" at c:\rnl\code with args { "--from-stdin", "c:\rnl\code\scratch.py", "-f", "json" }
[DEBUG 10/10/2022 08:32:31] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:319: spawning command "flake8" at c:\rnl\code with args { "--format", "default", "--stdin-display-name", "c:\rnl\code\scratch.py", "-" }
[DEBUG 10/10/2022 08:32:31] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:319: spawning command "mypy" at c:\rnl\code with args { "--hide-error-codes", "--hide-error-context", "--no-color-output", "--show-column-numbers", "--show-error-codes", "--no-error-summary", "--no-pretty", "--shadow-file", "c:\rnl\code\scratch.py", "c:\rnl\code\.null-ls_880363_scratch.py", "c:\rnl\code\scratch.py" }
[TRACE 10/10/2022 08:32:31] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:203: error output: No Python at '"c:\rnl\python310\python.exe'
[TRACE 10/10/2022 08:32:31] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:204: output: nil
[WARN 10/10/2022 08:32:31] ...ack\packer\start\null-ls.nvim/lua/null-ls/generators.lua:92: failed to run generator: ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:218: error in generator output: No Python at '"c:\rnl\python310\python.exe'
[TRACE 10/10/2022 08:32:35] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:203: error output: nil
[TRACE 10/10/2022 08:32:35] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:204: output: nil
[TRACE 10/10/2022 08:32:35] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:203: error output: nil
[TRACE 10/10/2022 08:32:35] ...t\null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:204: output: []
[TRACE 10/10/2022 08:32:35] ...ck\packer\start\null-ls.nvim/lua/null-ls/diagnostics.lua:181: received diagnostics from source 3
[TRACE 10/10/2022 08:32:35] ...ck\packer\start\null-ls.nvim/lua/null-ls/diagnostics.lua:182: {}
[TRACE 10/10/2022 08:32:35] ...ck\packer\start\null-ls.nvim/lua/null-ls/diagnostics.lua:181: received diagnostics from source 2
[TRACE 10/10/2022 08:32:35] ...ck\packer\start\null-ls.nvim/lua/null-ls/diagnostics.lua:182: {}
Beta Was this translation helpful? Give feedback.
All reactions