DeprecationWarning with python 3.7 on Windows 10
See original GitHub issueEDIT: THIS IS NOT RELATED TO LEADERF, PLEASE SEE https://github.com/vim/vim/issues/3117
<del>-
vim or neovim?
- [x ] vim
- neovim
-
vim --version
ornvim --version
: VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Feb 8 2018 15:00:34) Included patches: 1-1476 -
Output of
:echo has("python")
: -
Output of
:echo has("python3")
: -
Output of
:echo &pythondll
(only vim, not neovim): -
Output of
:echo &pythonthreedll
(only vim, not neovim): pythonthreeddll=python37.dll -
Output of
:py print(sys.version)
: -
Output of
:py3 print(sys.version)
: -
Operating system:
- Linux
- Mac OS X
- Windows
- Etc.
-
Configurations related to LeaderF in vimrc: set pythonthreedll=python37.dll
Describe your question, feature request, or bug.
I installed the latest python(https://www.python.org/downloads/release/python-370b3/) on my new PC, and explicitly use its dll for vim. Since the python version is quite new, some features Leaderf use is deprecated. Vim prints following error message when it starts up:
处理 C:\Users\bennyye\vimfiles\bundle\LeaderF\autoload\lfMru.vim 时发生错误:
第 10 行:
/must>not&exist/foo:1: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
FYI: https://github.com/ARM-DOE/pyart/issues/677 https://github.com/ARM-DOE/pyart/pull/675 </del>
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (6 by maintainers)
Top GitHub Comments
I think this issue is because the python3.7 version is not consistent with the version when compiling vim. I have installed the latest vim, with output of
:version
as below:You can see
-DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python36.dll\"
, so you should use python3.6 instead of python3.7.@Yggdroot I did google it and I came up with nothing outside of downgraing to python 3.6 which is not an acceptable solution. The error explicitely says that it’s a deprecation warning coming from LeaderF. If it is indeed an issue from something other than LeaderF, maybe there should be a solution somewhere in the documentation since I’m not the first one to run into this issue.
Regretfully I cannot use this plugin anymore because of this issue. I hope it gets resolved soon.