ZyX wrote: > The last proposal was using '_vim_runtimepath_' special item in sys.path > alongside with import hooks. I can hardly call this a consensus because > last my argument about why vim should use this magic was not replied to by > anybody.
I wonder if this gives sufficient flexibility. I suppose it's fine as a default, but what if the user wants a different order? > I do not remember whether it was discussed earlier, but for python/ > directories here is a proposal: python/ or pythonx/ is searched for modules > in both pythons, python2/ (or python/) and python3/ are searched only for > specific python versions. (pythonx/ appeared only after a patch from @Marc > Weber; second alternative (pythonx/ and python/) should be used in case > idea from this patch is considered good.) I suppose "pythonx" would be searched after python2 (for Python 2.x) and python3 (for Python 3.x). That seems like a straightforward solution. So, how do we implement this? -- Over the years, I've developed my sense of deja vu so acutely that now I can remember things that *have* happened before ... /// 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.
