I have issues with my python flags for (G)Vim. Even though I have enabled PYTHON_TARGETS="2.7 3.3" I only get Python 3 support, and no ordinary "python" support. I have this as my build flags for Gvim: root@skare$ emerge -pqv vim [ebuild R ] app-editors/vim-7.4.560 USE="X acl gpm nls perl python vim-pager -cscope -debug -lua -luajit -minimal -racket -ruby (-selinux) -tcl" PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4" PYTHON_TARGETS="python2_7 python3_3 python3_4" root@skare$ emerge -pqv gvim [ebuild R ] app-editors/gvim-7.4.560 USE="acl gnome gtk netbeans nls perl python session (-aqua) -cscope -debug -lua -luajit -motif -neXt -racket -ruby (-selinux) -tcl" PYTHON_SINGLE_TARGET="python3_3 -python2_7 -python3_4" PYTHON_TARGETS="python2_7 python3_3 -python3_4" but when checking :version in GVim this is what I have: Kod: -python +python3 I found the post in the forum that I have linked to the bug, which seems to have a patch for it, along with a question of whether it is a bug or not. Reproducible: Always Actual Results: Only support for Python 3 interpreter Expected Results: Support for both Python (2) and Python 3 interpreter
*** Bug 537178 has been marked as a duplicate of this bug. ***
It's not a bug, multiple implementation support was explicitly disabled during earlier issues with the (at the time) new python eclasses and the vim eclass. I've considered re-enabling multi implementation support after I got rid of the vim eclass recently (allowing easier changes between versions), but I haven't gotten around to it.
*** Bug 537606 has been marked as a duplicate of this bug. ***
It would be great to see it introduced again since more and more plugins are taking advantage of python3, but python 2 is still a bit too common to be removed completely.
(In reply to Tim Harder from comment #2) > It's not a bug. User requests both Python 2 and 3 support. User receives one or the other but not both with no ebuild output noting this to be the expected case. This is a bug. > multiple implementation support was explicitly disabled during earlier > issues with the (at the time) new python eclasses and the vim eclass. Is this still an issue? The forum thread at http://forums.gentoo.org/viewtopic-p-7689082.html suggests "Probably not." > I've considered re-enabling multi implementation support after I got rid of > the vim eclass recently (allowing easier changes between versions), but I > haven't gotten around to it. I need this. I can't be the only one. Until this resolves itself, I'll probably maintain a temporary "app-editors/vim" fork at my unofficial "raiagent" overlay. Needless to say, this is non-ideal. Thankfully, this is the only issue I've ever stumbled across with the Vim ebuilds. Thanks for the great work, intrepid maintainers.
Re-enabled in 7.4.622.
