On Thu, Feb 20, 2014 at 12:19:27PM +0200, İsmail Dönmez wrote: > I am the vim maintainer for openSUSE and SUSE Enterprise Linux so its not > that hard for me to test latest patches :-) > > But sadly going up to .182 doesn't fix the problem.
Ok, so vim implements a special module loader that can look for Python modules in runtimepath. This is described by :h python-special-path Now Python 3.4 changed the import machinery a bit, as described by PEP 451: http://legacy.python.org/dev/peps/pep-0451/ This PEP claims that it is fully backwards-compatible[1][2], which doesn't appear to be the case. Maybe file a Python bug about this? [1] http://legacy.python.org/dev/peps/pep-0451/#what-will-existing-finders-and-loaders-have-to-do-differently [2] http://legacy.python.org/dev/peps/pep-0451/#backward-compatibility I'm not very familiar with either codebase (vim or CPython), and despite working with Python for over 10 years I never felt the need to implement a custom module finder/loader. I'm not sure how much of a help I can be... Marius Gedminas -- At one job, for a short time my desktop HP (running HPUX) was being used as a print server. I soon found out that having something heavy in front of the plug was a good idea, after kicking it out of the outlet a couple of times. I used my old TRS-80 4P, doubtless the slowest computer ever to perform a critical function at that company. -- David Thornley
signature.asc
Description: Digital signature
