The [g]vim-7.3 currently in the tree is not set up to enable the new python3 support. This should be figured out. Probably everything will need to be done in vim.eclass and probably will need a new IUSE="python3".
Hi, Any chance for this? I've succesfuly compiled Vim 7.3 with Python3, the only thing that I did was to also specify --with-python3-config-dir= since it was not found atomatically.
Any status update on this one? Would be nice to have this in the tree. Also doing this move in one's own private overlay is not so easy because one needs to override an eclass, which is a bit involved.
Desperately need this feature. Python3 would be 4 years old at the end of 2012 but it's still not well supported.
(In reply to comment #1) > Hi, > > Any chance for this? I've succesfuly compiled Vim 7.3 with Python3, the only > thing that I did was to also specify --with-python3-config-dir= since it was > not found atomatically. The config dir thing sucks a bit. The subdirectory name has been changed to config-X.Y in py3.2 and I think upstream should update their configure checks for that rather than relying on us to hack that over.
I've just looked at hg tip and they seem to have tried to fix it. But it fails in Gentoo because we have sys.abiflags == '' and they assume it's always non-null for some reason... @vim, could you take that upstream? I will attach the eclass patches to the other bug.
7.3.905 in CVS now supports python3 and I'll upstream the configure patch that fixes the python3 configdir issue when sys.abiflags is empty.