Replies: 1 comment
-
|
A very delayed answer, but I ran into this myself today, wondering why it kept using 3.12 when 3.14 is my latest installed version. Well, it's hardcoded to try a bunch of different interpreter versions, with the maximum version being 3.12: mason.nvim/lua/mason-core/installer/managers/pypi.lua Lines 60 to 77 in ad7146a |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Mason is latching onto a python install that is not the one I want. I am setting the one I want in my PATH, then launching nvim. But :checkhealth shows that Mason is not find the one in my PATH. I do not have g:python3_host_prog set.
I am working from a clean git-clone of kickstart.nvim.
In case it matters, I'm using NVIM_APPNAME to target my kickstart.nvim install.
Figured it out. I had changed my shell env PATH var, but I had not changed it in my .bashrc. Looks like Mason is using login shells to find stuff. I'm ok to move forward, but this doesn't seem like the right thing for Mason to do.
Beta Was this translation helpful? Give feedback.
All reactions