As I discovered while discussing the Python path patch with Vim's upstream[0], the patch I suggested to fix these bugs only works if the libc follows SUS' definition[1] of how realpath(3) works.
Specifically, it must return NULL when given an empty string for the path. At least FreeBSD instead returns the current working directory of the process[2], which means that removing the empty elements from sys.path no longer has an effect. When sending bug reports to your respective upstream, I'd suggest either adjusting the patch to simply remove the first element of sys.path or give a garbage path to PySys_SetArgv and explicitly filter that out of sys.path (as was done by Vim's upstream[3]). [0] - http://bugs.debian.org/493937 [1] - http://www.opengroup.org/onlinepubs/009695399/functions/realpath.html [2] - http://www.freebsd.org/cgi/query-pr.cgi?pr=128933 [3] - http://ftp.vim.org/pub/vim/patches/7.2/7.2.045 -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
