>Do we need this kind of magic? Updating sys.path is much simpler and >also does not hide what we are doing (in case someone is debugging >what's going on). The only trick we need is when the user changes >'runtimepath'. But that would happen very infrequently.
There are two other big advantages of this “magic”: user did not loose control over `sys.path` and it can be written in pure python. All advantages in a list: it … 1. makes it possible to specify which directories should be searched before plugin ones and which after; 2. makes it possible to remove vim paths from sys.path completely and not ever have problems with vim adding them again; 3. can be written in pure python and fallback implementation for old vims (the ones even without vim.eval) can be created; 4. makes hacking non-if_py* C files not needed. There is a reason for coding it in C though (and porting @Xavier de Gaye file to C as well): this makes vim core functionality independent of presence of runtime files. There is a reason for not coding it in C as well: it is faster to write in python and even being written in python this will not have problems with performance (it’ll in any case waste much time on IO). -- -- 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.
