2008/11/3 Ben Schmidt <[EMAIL PROTECTED]>: > > You could ask the Python guys to try to find out exactly what the API > changes are and whether they apply to Vim or not, but this could be > difficult to ascertain--these things tend to be a bit of a haystack. On > the other hand, it could be the change is very simple and irrelevant, > and you can just somehow disable the warning--if this is a likely > scenario, the Python guys almost certainly will have provided a way to > disable it.
I don't think it is a feasible solution...e.g. what happens the next time the API changes? No, I think loading Python dynamically is out of the question. :( > If it can't be ascertained whether change is irrelevant, or it can be > ascertained that it *is* relevant, it would be technically possible to > make a Vim that worked with both API versions, but you'd have to > basically duplicate if_python.c, change all the function names so there > were two versions of each, compile one against the 2.3 API and another > against the 2.5 API and then have a runtime check to decide which > version of the functions to call. It would be quite a refactoring job, > and I would say not worth the effort. Ugh, yeah, that's no good either. > One definite solution, though not ideal, but which is easy to set up for > building, as well as easy for users to understand: have separate MacVim > builds for Tiger and Leopard. Stacks of apps do it, and Mac users are > fairly used to downloading the version appropriate to their OS version. It seems this is the only way to go then. But...I wonder if it really is worth my time making two distributions just so a few users get to use Python 2.5 instead of 2.3. I think I need a better reason than that for something as drastic as distributing two different versions of the binary. Maybe I underestimate the number of users who would benefit from 2.5, but for now I'll just keep building with 2.3. :-/ Thanks to everybody for the feedback, Björn --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
