Hi Reckoner!
On Fr, 08 Jan 2016, Reckoner wrote:
> Hi,
>
> Using Miniconda, I use multiple Python versions on my Windows 10 workstation.
> I
> also use many Python VIM extensions. The problem is that VIM wants to
> internally use a conflicting Python version. In other words, suppose I have
> two
> Python installations,
>
> c:\python27
> d:\miniconda2
>
> When I'm working with the miniconda2 Python version, I still need the Python
> VIM plugins to reference the c:\python27 installation. Environment variables
> like PYTHONHOME/PYTHONPATH do not help here because when VIM seeks out a
> Python
> version, it picks those up and they point to the wrong Python
> installation.
>
> I have been trying (with limited luck using the Visual Studio 2015 Community
> edition) to re-build GVIM. I am unable to figure out if it is possible during
> the build process to hard-wire VIM and its Python plugins to only use the c:\
> python27 installation.
>
> Any ideas appreciated.
>
> Thanks!
That should be possible. Also I think, setting PYTHONHOME only works
since version 7.4.1012
Best,
Christian
--
Die Statistik ist die erste der ungenauen Wissenschaften.
-- Edmond de Goncourt
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
