ZyX wrote: > Reason: for <python-2.2 vim won’t compile in any case: there are no > iterator objects and thus my old change (with vim.bindeval) won’t > compile or (in case using dynamic library loading) run: <python-2.2 is > already not supported. Additionally <python-1.5 (1.6 till 2.1 were not > checked) requires varargs.h which none of C compilers I have support. > > Note that even with python-2.2 vim requires two changes in order to > compile and not crash afterwards (removing absent PyBool_Check (for > compiling) and assigning saved_python_thread at first > PyEval_SaveThread call (in order not to crash)).
So we would require at least Python 2.3, right? It was released in 2003, ten years ago. I think that would be OK, unless there is a system that is stuck with Python 2.2. -- "After a few years of marriage a man can look right at a woman without seeing her and a woman can see right through a man without looking at him." - Helen Rowland /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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/groups/opt_out.
