2015-09-16 0:14 GMT+03:00 Markus Meskanen <vim-dev-git...@256bit.org>:
> I installed Python 3.5 (tried with both 32- and 64-bit versions), but my > Vim is unable to recognize the version. > Apparently I would have to recompile the whole Vim to work with any other > version than Python 3.2. > Here <http://i.imgur.com/x1O5Sq9.png> are some of the errors I'm > receiving, all of them basically leading up to Could not load library > python32.dll, which I don't have because I'm using python35.dll. > > This might not be a bug for you guys, but it's 2015 and every other text > editor I've ever used automatically recognizes and can run any Python > version I have installed. > Which editors? Some of them use Python as an external executable and use some IPC method for communication and thus do not require recompiling. Some are written in Python (which has good backward compatibility inside one major version) and do not require recompiling as well. Vim on the other side is *embedding* Python using its C API. It cannot possibly use any Python version, given that “backward compatibility” here sometimes means that “we can replace C function with a C macros”. This is rather unique: even NeoVim prefers to run python as a child process and communicate with it using sockets, thus being version-independent as long as neovim module runs on given Python version and implementation. > I personally think it would be about time for Vim to upgrade its system a > little, so it wouldn't be necessary for an everyday user to learn how to > compile Vim and change its Python version. > C API is the fastest way to work with Python. Everything else will be slower. Also this code is already written. > If there's something I've missed, please elaborate, I'm just a beginner > with Vim. But if this is the case and no change is going to be made, I feel > like Vim is not too friendly for Python developers, and I will have to > revert to an other editor. Which would be unfortunate, because Vim seems > like an awesome text editor, but some of its features are still from 1990. > Just my opinion. > > — > Reply to this email directly or view it on GitHub > <https://github.com/vim/vim/issues/419>. > > -- > -- > 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 vim_dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
