On Sun, Feb 15, 2009 at 02:57:35PM +0100, Bram Moolenaar wrote: > I haven't looked at the patch yet, but I would like to encourage others > to help make this work for as many systems as possible. It's so much > nicer when Vim can be build with Python and the binary distributed to > systems where Python is not available. Less versions, more flexibility. > > I assume that for building the Python headers and tools are still > required, thus it only helps for when distributing a Vim binary.
Correct. One question I have is how flexible it should be. I did this the way I did because I could easily hang off the work that had been done for Windows, but if I were to make a dynamic module -- consisting of if_python.o and py_config.o -- then I could make one for each version of Python available on the system at build time, and then try loading them in turn until one was successful. So you could build on a system that had 2.4, 2.5, and 2.6, and work on a system that had any of the three. Of course, fully fleshing that idea out means giving some control to the user of which version they want to use, or a preference ordering of the versions. And further down that road would be to experiment with whether multiple versions of Python can be loaded into memory at the same time. If that's the case, then you could have different scripts running with different versions in the same vim session. I don't know how useful that would be in practice, though. Danek --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
