summaryrefslogtreecommitdiffstats
path: root/lldb/third_party/Python/module/six/six.py
Commit message (Collapse)AuthorAgeFilesLines
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-10/+29
| | | | | | | | | | | | | | | | | | | | | | | *** to conform to clang-format’s LLVM style. This kind of mass change has *** two obvious implications: Firstly, merging this particular commit into a downstream fork may be a huge effort. Alternatively, it may be worth merging all changes up to this commit, performing the same reformatting operation locally, and then discarding the merge for this particular commit. The commands used to accomplish this reformatting were as follows (with current working directory as the root of the repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ; The version of clang-format used was 3.9.0, and autopep8 was 1.2.4. Secondly, “blame” style tools will generally point to this commit instead of a meaningful prior commit. There are alternatives available that will attempt to look through this change and find the appropriate prior commit. YMMV. llvm-svn: 280751
* Add `six` Python module to lldb/third_party.Zachary Turner2015-10-201-0/+868
Six is a python module designed to smooth the process of porting Python 2 code to Python 3. Specifically, six provides a consistent interface to some of the breaking changes between 2 and 3. For example, the syntax for assigning a metaclass differs in Python 2 and 3. Six addresses this by providing a single class decorator that will do the right thing depending on which version of Python is being run. There are other examples too, such as dealing with renamed modules, unicode literals, etc. llvm-svn: 250857
OpenPOWER on IntegriCloud