Closed aeberspaecher closed 4 years ago
Is related to #10898?
@sebhahn, I don't think so as I can select virtual environments.
The problem still persists in recent master (e33638d9). I am certain the problem is in spacemacs/pyenv-executable-find
because my problem is fixed if I comment out all the logic besides the closing (executable-find command)
.
Can anyone take me through the function's intentions? Perhaps @cpaulik who wrote the code? What is considered the correct executable path to return in case pyenv uses system Python?
The original intention was to not fall back to the system executable automatically. See https://github.com/syl20bnr/spacemacs/pull/9348
If a user has selected the system interpreter in ´pyenv´ then the function should return the system version of the executable.
Looking at the function again it does at the moment indeed return ´nil´ if the executable is not in the same path as the activated pyenv environment. So we might need a special case in the function for treating the ´system´ environment.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!
Description :octocat:
nil
considered a valid Python interpreter.Reproduction guide :beetle:
SPC m c c
Observed behaviour: :eyes: :broken_heart:
On a system with pyenv and pyenv-which-ext that uses system Python,
spacemacs/pyenv-executable-find
returns nil instead of a path to the system Python executable.SPC m c c
on a Python file callsnil
as the Python interpreter.Expected behaviour: :heart: :smile:
Script executes using system Python/IPython.
System Info :computer:
Backtrace :paw_prints: