Le lundi 22 janvier 2018 00:33:49 UTC+1, Ken Takata a écrit :
> Hi,
>
> 2018/1/22 Mon 3:27:56 UTC+9 Ni Va wrote:
> > Le dimanche 21 janvier 2018 15:47:15 UTC+1, Ken Takata a écrit :
> > > Hi,
> > >
> > > 2018/1/21 Sun 23:40:20 UTC+9 Ni Va wrote:
> > > > Le vendredi 19 janvier 2018 12:06:22 UTC+1, Ken Takata a écrit :
> > > > > Hi,
> > > > >
> > > > > 2018/1/19 Fri 19:49:18 UTC+9 Ni Va wrote:
> > > > > > 1. I delete registry entry
> > > > > >
> > > > > >
> > > > > > 2. in _vimrc
> > > > > >
> > > > > >
> > > > > > " Python
> > > > > >
> > > > > > let $pythonhome= 'c:/thirdPartTools/Python36'
> > > > > > let currpath.=';'.'c:/thirdPartTools/Python27'
> > > > > > let currpath.=';'.'c:/thirdPartTools/Python36'
> > > > > > let currpath.=';'.'c:/thirdPartTools/Python36/Lib/site-packages'
> > > > > > let uniqPath= join(uniq(split(currpath,';')),';')
> > > > > > let $path=currpath
> > > > > >
> > > > > > set pythondll=python27.dll
> > > > > > set pythonthreedll=python36.dll
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > 3. py3 print('hell') returns hell => OK
> > > > > >
> > > > > >
> > > > > > 4. echo neovim_rpc#serveraddr() returns local ip server => OK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Distri is now standalone.
> > > > > >
> > > > > >
> > > > > > Thank you !
> > > > >
> > > > > I suspect that `:py print('hello')` doesn't work now.
> > > > > There is a PR to fix it, but it is not included:
> > > > > https://github.com/vim/vim/pull/1266
> > > > >
> > > > > Regards,
> > > > > Ken Takata
> > > >
> > > > As you said, py print('hello') not loaded when py3 loaded with the
> > > > following minimal set in _vimrc:
> > > >
> > > >
> > > > I Focus on
> > > > 1. rpc server started OK from
> > > > https://github.com/roxma/vim-hug-neovim-rpc.git
> > > > 2. deoplete from https://github.com/Shougo/deoplete.nvim.git seems OK
> > > > 3. clang_complete from https://github.com/Rip-Rip/clang_complete.git is
> > > > KO
> > > >
> > > >
> > > >
> > > >
> > > > " Python minimal set with windows cleaned up registry
> > > > let pythonver=36
> > > >
> > > > let $pythonhome= thirdpartbase.'/Python'.pythonver
> > > > let $pythonpath= $pythonhome
> > > > for path in split(globpath($pythonhome,'*'),'\n')
> > > > let $pythonpath.=';'.path
> > > > endfor
> > > > for path in split(globpath($pythonhome.'/Lib/site-packages','*'),'\n')
> > > > let $pythonpath.=';'.path
> > > > endfor
> > > >
> > > > let $path.=';'.$pythonhome
> > > > let $path.=';'.$pythonhome.'/scripts'
> > > > let $path.=';'.$pythonpath
> > > >
> > > > " set pythondll=python27.dll
> > > > " set pythonthreedll=python36.dll
> > > >
> > > > call join(uniq(split($path,';')),';')
> > >
> > > The problem is that Python 2 and 3 share the same evironment variable.
> > > To solve this, as I already said, PR#1266 is required.
> > >
> > > Regards,
> > > Ken Takata
> >
> > And is it working ?
>
> Of course not, if you don't apply the PR and fix conflicts by yourself.
> The PR hasn't been merged yet.
> Also note that the PR adds two options 'pythonhome' and 'pythonthreehome',
> not the support for the environment variable $PYTHONTHREEHOME.
>
>
> > Because when I mix pythonhome and pythonthreehome with associated paths to
> > pythonpath.
>
> I don't know about the $PYTHONPATH environment variable, whether it can be
> safely shared between Python 2 and 3, or sys.path should be set separately
> in if_python.
>
> Regards,
> Ken Takata
Considering that $pythonpath feed just for one python's version 36:
c:/ThirdPartTools/Python36
c:\ThirdPartTools\Python36\DLLs
c:\ThirdPartTools\Python36\Doc
c:\ThirdPartTools\Python36\include
c:\ThirdPartTools\Python36\Lib
c:\ThirdPartTools\Python36\libs
c:\ThirdPartTools\Python36\LICENSE.txt
c:\ThirdPartTools\Python36\NEWS.txt
c:\ThirdPartTools\Python36\python.exe
c:\ThirdPartTools\Python36\python3.dll
c:\ThirdPartTools\Python36\python3.exe
c:\ThirdPartTools\Python36\python36.dll
c:\ThirdPartTools\Python36\pythonw.exe
c:\ThirdPartTools\Python36\Scripts
c:\ThirdPartTools\Python36\Tools
c:\ThirdPartTools\Python36\vcruntime140.dll
c:\ThirdPartTools\Python36\Lib\site-packages\easy_install.py
c:\ThirdPartTools\Python36\Lib\site-packages\greenlet-0.4.12.dist-info
c:\ThirdPartTools\Python36\Lib\site-packages\greenlet.cp36-win_amd64.pyd
c:\ThirdPartTools\Python36\Lib\site-packages\msgpack
c:\ThirdPartTools\Python36\Lib\site-packages\msgpack-0.5.1.dist-info
c:\ThirdPartTools\Python36\Lib\site-packages\msgpack_python-0.5.1-py3.6.egg-info
c:\ThirdPartTools\Python36\Lib\site-packages\neovim
c:\ThirdPartTools\Python36\Lib\site-packages\neovim-0.2.0-py3.6.egg-info
c:\ThirdPartTools\Python36\Lib\site-packages\pip
c:\ThirdPartTools\Python36\Lib\site-packages\pip-9.0.1.dist-info
c:\ThirdPartTools\Python36\Lib\site-packages\pkg_resources
c:\ThirdPartTools\Python36\Lib\site-packages\pyuv
c:\ThirdPartTools\Python36\Lib\site-packages\pyuv-1.4.0.dist-info
c:\ThirdPartTools\Python36\Lib\site-packages\README.txt
c:\ThirdPartTools\Python36\Lib\site-packages\setuptools
c:\ThirdPartTools\Python36\Lib\site-packages\setuptools-28.8.0.dist-info
c:\ThirdPartTools\Python36\Lib\site-packages\__pycache__
:py3 print('hell') It works !
Concatenate $pythonpath with c:\ThirdPartTools\Python27 path,
:py3 print('hell') It fails !
--
--
You received this message from the "vim_dev" 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_dev" 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.
