On Tue, Feb 17, 2009 at 07:32:35PM +0100, björn wrote: > Yes that is all I am after -- I can't see any particular use for > having two or more co-resident. (?)
The use case would be if you had a script that could only run with 2.3 and another that could only run with 2.6, and you wanted to use both in the same vim process. I agree that it's all that worth worrying about, though. > I think this is overkill. Why not just see which modules are > installed and try loading from newest to oldest? Works for me. I can always change it later to be fancier if people find the simple method to not be enough. > Well, maybe it isn't that simple since loading will probably work as long > as the module is present even if the matching python version is not > installed. That'll probably depend on the features of the dynamic linker. On Solaris, at least, the module will fail to load if a dependency it has isn't there. I may not get to it before this weekend, but I'll post another patch as soon as I have it. In the meantime, if you have a chance to try my latest patch out on OS X, I'd be curious to know if it works there. Thanks, Danek --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
