Davido wrote: > Bram Moolenaar <[email protected]> wrote, on mar 11 jun 11:46 : > > > > > Davido wrote: > > > > > Bram Moolenaar <[email protected]> wrote, on lun 10 jun 21:27 : > > > > > > > > > > > Patch 7.3.1163 > > > > Problem: Not easy to load Python modules. > > > > Solution: Search "python2", "python3" and "pythonx" directories in > > > > 'runtimepath' for Python modules. (ZyX) > > > > Files: runtime/doc/if_pyth.txt, src/configure.in, src/ex_cmds2.c, > > > > src/if_py_both.h, src/if_python.c, src/if_python3.c, > > > > src/testdir/test86.in, src/testdir/test87.in, > > > > src/auto/configure > > > > > > Hello, > > > > > > It seems to cause problems with some python based plugins ; I guess > > > it comes from this patch, since a yesterday vim build worked perfectly : > > > > > > Error treating [...]/vim-addon-manager/UltiSnips/plugin/UltiSnips.vim : > > > ligne 251 : > > > Traceback (most recent call last): > > > File "<string>", line 1, in <module> > > > ImportError: No module named UltiSnips > > > ligne 252 : > > > Traceback (most recent call last): > > > File "<string>", line 1, in <module> > > > NameError: name 'UltiSnips_Manager' is not defined > > > ligne 253 : > > > Traceback (most recent call last): > > > File "<string>", line 1, in <module> > > > NameError: name 'UltiSnips_Manager' is not defined > > > ligne 254 : > > > Traceback (most recent call last): > > > File "<string>", line 1, in <module> > > > NameError: name 'UltiSnips_Manager' is not defined > > > > > > I've tried to symlink the python dir to pythonx or plugin/pythonx (or > > > 2,3), but it doesn't work. > > > > > > Similar issue with Ozzy. > > > > > > Is it intended behaviour, and the plugins will adjust in time ? > > > > The change must be backwards compatible. Where is the UltiSnips python > > file located? > > All the python files seem located in plugin/UltiSnips, but you > have some subdirs inside it. Here is the tree : > > [...]/vim-addon-manager/UltiSnips/plugin/UltiSnips > > __init__.py > __init__.pyc > _diff.py > _diff.pyc > _vim.py > _vim.pyc > compatibility.py > compatibility.pyc > compatibility_py2.py > compatibility_py2.pyc > compatibility_py3.py > debug.py
[...] Hmm, that's a lot of files. So how did it find these (or at least the one included from Vim script) before? Does it specify a path in the "import"? -- hundred-and-one symptoms of being an internet addict: 143. You dream in pallettes of 216 websafe colors. /// 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.
