Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Experimental] Set pythonhome and pythonthreehome automatically #423

Merged
merged 2 commits into from Nov 29, 2016

Conversation

splhack
Copy link
Contributor

@splhack splhack commented Nov 29, 2016

No description provided.

It is really difficult to set Python home directory properly for Python
2.7 and 3.5 in .vimrc at the same time since both versions use `$PYTHONHOME`
environment variable. Introduce `pythonhome` and `pythonthreehome`
options in order to set Python home directory via `Py_SetPythonHome` API
for both versions.
global
{not in Vi}
{only available when compiled with the |+python/dyn|
feature}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this have an "only in MacVim" disclaimer?

global
{not in Vi}
{only available when compiled with the |+python3/dyn|
feature}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this have an "only available in MacVim" disclaimer?

MacVim uses Homebrew python2 if installed, otherwise System's
MacVim uses Homebrew python3 if installed, next try to use python.org binary
@splhack splhack merged commit 1b15a71 into master Nov 29, 2016
@splhack splhack deleted the experimental/pythonhomeopt branch November 29, 2016 06:13
raimue added a commit to macports/macports-ports that referenced this pull request Sep 20, 2017
MacVim preferred python from /usr/local at runtime, if it existed.
Always use the python version it was configured with.

Upstream: macvim-dev/macvim#423 (reverting partly)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants