You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Bug 21920 a problem is described that makes Python very difficult to use on Windows. Python 3.5 on Windows is implemented in such a way as to be forward compatible with future versions of Visual Studio. As a result, we've decided that the best way forward is to allow LLDB to support Python 3.5. Since there are already potentially hundreds of thousands of lines of Python code written against 2.7, we will need to do this in such a way that LLDB supports both Python 2.7 and Python 3.5+.
The biggest difficulty and pain point arising from this will be the need for the test suite and all specific tests to be written using a subset of Python that will work in both 2.7 and 3.5.
In order to ensure this requirement is met, part of this task will involve setting up at least two build bots: one that runs tests using 2.7 and another that runs tests using 3.5.
The text was updated successfully, but these errors were encountered:
Extended Description
In Bug 21920 a problem is described that makes Python very difficult to use on Windows. Python 3.5 on Windows is implemented in such a way as to be forward compatible with future versions of Visual Studio. As a result, we've decided that the best way forward is to allow LLDB to support Python 3.5. Since there are already potentially hundreds of thousands of lines of Python code written against 2.7, we will need to do this in such a way that LLDB supports both Python 2.7 and Python 3.5+.
The biggest difficulty and pain point arising from this will be the need for the test suite and all specific tests to be written using a subset of Python that will work in both 2.7 and 3.5.
In order to ensure this requirement is met, part of this task will involve setting up at least two build bots: one that runs tests using 2.7 and another that runs tests using 3.5.
The text was updated successfully, but these errors were encountered: