[lldb-dev] Python 3 and dotest
Zachary Turner via lldb-dev
lldb-dev at lists.llvm.org
Tue Oct 13 09:45:02 PDT 2015
On Mon, Oct 12, 2015 at 7:31 PM Zachary Turner <zturner at google.com> wrote:
> Moving this to the public list because it seems useful to see what other
> members of the community have to say as well.
BTW , I realized I didn't give any context here and it's hard to follow a
long quote thread. Mostly this is just to give a heads up that support for
Python 3 in LLDB is -- at a minimum -- coming, so I want to find out who
(if anyone) is interested in this and how people plan to use it (or not use
I'm sure the first question is probably "Why are you doing this?". The
short version is that it's quite literally the only path forward on
Windows. There is no way to transition to the next version of the compiler
without moving to Python 3.5 or greater. If you want the long version, let
The biggest challenge (which is what most of the quote thread is about) is
going to be having dotest support both Python 2 and Python 3
simultaneously. LLDB supporting both at the native level shouldn't be a
problem, it's mostly about writing Python code inside of dotest that works
in both 2 and 3.
This will be the first time I've tried porting a large Python codebase to
Python 3, so I'm open for suggestions on how to minimize the impact of
this. Currently I'm of the mind that the onus should be on the person
checking in a test (or a change to the test suite) to make sure it works in
both versions of Python. We'll eventually have a build bot running each
version, so you should know when it breaks the other version (assuming you
don't test the other version beforehand, which you should).
I expect this is going to be unpleasant at best, so if anyone has any
suggestions, I'm all ears. The quote thread -- if you happened to read the
whole thing -- was about an idea to have dotest only support python 3.
Again, LLDB itself would continue to support python 2. Just that it would
require Python 3 to run the test suite. I imagine there's only ~20 people
anywhere running the test suite, and a couple of build bots, so this seems
like a reasonable option to me, but obviously I don't have everyone else's
Anyway. Questions, comments, concerns feel free to respond and I'll answer
as best I can.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev