-
Notifications
You must be signed in to change notification settings - Fork 24
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
Getting a deprecation warning using python 3.7 #44
Comments
I resolved by doing: brew reinstall vim --with-python@2 from vim/vim#3117 |
Glad that worked out for you! Unfortunately I'm on Ubuntu and need to compile vim with python3 support. Hopefully a similarly easy solution comes up for this situation. |
So am I! It seems that it is just a package rename problem (using But the problem is not knowing where the python import code locates. I had try to run |
I think it's something deeper than that.. Line 28, which errors, is part of this block of code: 19 let s:script_folder_path = escape( expand( '<sfile>:p:h' ), '\' )
20 if has('python')
21 " Python 2
22 py import sys
23 py import vim
24 exe 'python sys.path = sys.path + ["' . s:script_folder_path . '/../python"]'
25 py import mta_vim
26 else
27 " Python 3
28 py3 import sys
29 py3 import vim
30 exe 'python3 sys.path = sys.path + ["' . s:script_folder_path . '/../python"]'
31 py3 import mta_vim
32 endif Yeah I think this is out of my hands here, it's using It'd probably be helpful if we pasted our |
Agree with I had try ommit MatchTagAlways plug, and then restart vim, this infomation comes again. So my judgment is that the problem is in some basic code, and then it affects the normal operation of most plugins. |
Regardless of installed plugins, silently execute python3 once on the top of your
|
:echo has('python') => 0
:echo has('python3') => 1
I don't see anyone else talking about this so I reckon I might be doing something wrong?
I compiled vim from source with python3 (not python2) and I pointed it at my python 3.7 directory.
Anything I can do?
The text was updated successfully, but these errors were encountered: