New issue 1856: initpath.find_executable bug https://bitbucket.org/pypy/pypy/issue/1856/initpathfind_executable-bug
David Ripton: If a user has "::" somewhere in his PATH (bogus, but not uncommon), and has a file called "pypy" in the current directory, then running pypy (from elsewhere on the PATH, like /usr/bin) causes pypy to exit with the error: debug: WARNING: Library path not found, using compiled-in sys.path. debug: WARNING: 'sys.prefix' will not be set. debug: WARNING: Make sure the pypy binary is kept inside its tree of files. debug: WARNING: It is ok to create a symlink to it from somewhere else. debug: OperationError: debug: operror-type: ImportError debug: operror-value: No module named os The problem is that initpath.find_executable does not filter out null directories from the PATH. Marking as trivial because this is such an odd combination of circumstances that probably nobody else has ever run into it, but I'll submit a patch for it anyway. (It's a trivial fix.) _______________________________________________ pypy-issue mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-issue
