summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/TestCPPBreakpointCommands.py
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-07-18 15:17:42 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-07-18 15:17:42 +0000
commita5359b1b0754ff70b0a36917a5e61625c951b408 (patch)
treed3a9727ff3a27ecebc868b1e1ef4fb1f18e51517 /lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/TestCPPBreakpointCommands.py
parentac958c2ed6ab6f4160194b8d0d9752db73bcb03c (diff)
downloadbcm5719-llvm-a5359b1b0754ff70b0a36917a5e61625c951b408.tar.gz
bcm5719-llvm-a5359b1b0754ff70b0a36917a5e61625c951b408.zip
[CMake] Don't set Python_ADDITIONAL_VERSIONS
Until recently, Python_ADDITIONAL_VERSIONS was used to limit LLVM's Python support to 2.7. Now that both LLVM and LLDB both support Python 3, there's no longer a need to put an arbitrary limit on this. However, instead of removing the variable, r365692 expanded the list, which has the (presumably unintentional) side-effect of expression preference for Python 3. Instead, as Michal proposed in the original code review, we should just not set the list at all, and let CMake pick whatever Python interpreter you have in your path. This patch removes the Python_ADDITIONAL_VERSIONS variable in llvm, clang and lld. I've also updated the docs with the default behavior and how to force a different Python version to be used. Differential revision: https://reviews.llvm.org/D64894 llvm-svn: 366447
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/TestCPPBreakpointCommands.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud