On Tuesday, 17 April 2012 22:11:07 UTC+8, Xavier de Gaye wrote: > This thread of the python-devel mailing list describes the issues > raised by the change in 2.7.3 that removed urandom from the stdlib > module os.py: > > http://thread.gmane.org/gmane.comp.python.devel/131382 > > One of the participants in this thread wrote a page explaining the > issue: > > http://piratepad.net/PAZ3CEq9CZ > > > 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 It is still taking up 2.7.2+ ( I am not not sure where it is taking from. config.log details are here: http://paste.pocoo.org/show/583031/ I suspect at at one line it take -Ipython2.7 and I guess, it going to other python interpreter. Thanks, Senthil -- 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
