ZyX wrote: > > Did you see the other message, that loading a module the old way stopped > > working? We should support backwards compatibility, otherwise all > > existing plugins that load a Python module suddenly stop working. > > Was not intended. It appears that currently the only option is to have > this special directory be the last one in sys.path or not have it at > all in python 2. In python 3 where authors have provided easy access > to internals everything works fine. > > I will investigate the issue further. Currently I can only say that if > I try to use import with trailing directories in a living system bug > does appear (for python-2* only), but the following tests work in both > pythons which is rather strange: > > diff -r 7fda29626053 src/testdir/python_before/after.py
This should probably have been python_after. Anyway, in the other message you mention that the problem is with package initialization, not with directly loaded files as in this test. Right? -- We are the Borg of GNU GPL. We will assimilate your source code. Resistance is futile. /// 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.
