On Tue, Apr 17, 2012 at 5:00 PM, Senthil Kumaran wrote: > On Tuesday, 17 April 2012 22:11:07 UTC+8, Xavier de Gaye wrote: >> If you do not see 2.7.3 when you run: >> >> :python import sys; print sys.version >> >> then it is because you are running in Vim an "older Python executable >> (which does not have an implementation of urandom), but then >> references the newer standard library (in which the os module also >> does not have an implementation of urandom)." > > > 2.7.2+ (2.7:0c10061df711, Jan 4 2012, 00:27:06) > [GCC 4.5.2] > Press ENTER or type command > > That's indeed the case, but I wonder how vim is referencing this older python > executable. > > I set the PATH=/home/senthil/localpython/bin:$PATH > > And then do > > ./configure --enable-pythoninterp > --with-python-config-dir=/home/senthil/localpython/lib/python2.7/config > --with-features=huge --prefix=/home/senthil/local
The following line in your config.log explains the problem: configure:5427: gcc -o conftest -g -O2 -I/home/senthil/localpython/include/python2.7 -DPYTHON_HOME=\"/home/senthil/localpython\" -pthread -I/usr/local/include -L/usr/local/lib conftest.c -lselinux -L/home/senthil/localpython/lib/python2.7/config -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic >&5 The link is done against python 2.7.2 with -lpython2.7, but it is done while referencing python 2.7.3 standard library with -DPYTHON_HOME=\"/home/senthil/localpython\" I believe it is best to avoid having two different python minor versions on the same system. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net -- 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
