lambdalisue / lambdalisue/vim-pyenv
RFC: Shouldn't vim-pyenv depends on vim's compile options?
Nobody has claimed this yet.
- Dominant language
- Vim Script
- Stars
- 107
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
When I use vim compiled with option "+python3" to edit python file on python2 environment set by pyenv
or I use vim compiled with option "+python" to edit python file on python3 environment set by pyenv,
vim-pyenv raise a error and say "vim-pyenv: Failed to activate "%s". Python version of the env is not supported in this Vim".
This behavior seems to be not favorable.
It force us to use vim +python3 enabled on python3 file and use vim enabled +python on python file.
After just commenting out the code where to check vim's option in vim-env,
vim-pyenv still work well on my environment in the situation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the vim-env code that checks Vim's +python or +python3 compile option during environment activation. Reproduce the failure with a Vim build and pyenv environment using different Python versions, then verify that activation no longer rejects this combination while preserving supported-environment behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, vim
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100