[Lldb-commits] [PATCH] D112973: [lldb] make it easier to find LLDB's python

[Jim Ingham via Phabricator via lldb-commits]

jingham added a comment.

Since you do need to match the lldb module to the python it was built against, this seems a useful addition.

The original --python-path was a bit unfortunate, we're supposed to be able to support multiple scripting interpreters (currently python & lua) and it would be annoying to have to add one of these variables for each scripting language we support.  So it seems a shame to repeat that error.

Maybe it would be better to have:

--scripting-module-path {python, lua}

and

--scripting-executable-path {python, lua}

as the arguments to the driver (we'll have to keep the --python-path for compatibility.)

Seems like "where is your module" and "where is your executable" are also questions we should be asking the ScriptInterpreter base class, and not going straight to the Python interpreter.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D112973/new/

https://reviews.llvm.org/D112973