Android: Workaround prebuilt python issue
am: aa8a88f3a9

Change-Id: I783ae40db4aa9739fd5178c86ccd2130d67cc190
tree: 976970568bb3d1710b016c70e943d481d1ac096d
  1. LICENSE
  2. METADATA
  3. MODULE_LICENSE_BSD
  4. MODULE_LICENSE_CC
  5. NOTICE
  6. OWNERS
  7. README.md
  8. Rguide.md
  9. Rguide.xml
  10. angularjs-google-style.html
  11. cppguide.html
  12. cppguide.xml
  13. cpplint/
  14. docguide/
  15. eclipse-cpp-google-style.xml
  16. eclipse-java-google-style.xml
  17. google-c-style.el
  18. google-r-style.html
  19. google_python_style.vim
  20. htmlcssguide.html
  21. htmlcssguide.xml
  22. include/
  23. intellij-java-google-style.xml
  24. javaguide.css
  25. javaguide.html
  26. javaguidelink.png
  27. javascriptguide.xml
  28. jsguide.html
  29. jsoncstyleguide.html
  30. jsoncstyleguide.xml
  31. jsoncstyleguide_example_01.png
  32. jsoncstyleguide_example_02.png
  33. lispguide.xml
  34. objcguide.md
  35. objcguide.xml
  36. pyguide.md
  37. shell.xml
  38. styleguide.css
  39. styleguide.xsl
  40. vimscriptfull.xml
  41. vimscriptguide.xml
  42. xmlstyle.html
README.md

Google Style Guides

Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a consistent style.

“Style” covers a lot of ground, from “use camelCase for variable names” to “never use global variables” to “never use exceptions.” This project (google/styleguide) links to the style guidelines we use for Google code. If you are modifying a project that originated at Google, you may be pointed to this page to see the style guides that apply to that project.

This project holds the C++ Style Guide, Objective-C Style Guide, Java Style Guide, Python Style Guide, R Style Guide, Shell Style Guide, HTML/CSS Style Guide, JavaScript Style Guide, AngularJS Style Guide, Common Lisp Style Guide, and Vimscript Style Guide. This project also contains cpplint, a tool to assist with style guide compliance, and google-c-style.el, an Emacs settings file for Google style.

If your project requires that you create a new XML document format, the XML Document Format Style Guide may be helpful. In addition to actual style rules, it also contains advice on designing your own vs. adapting an existing format, on XML instance document formatting, and on elements vs. attributes.

The style guides in this project are licensed under the CC-By 3.0 License, which encourages you to share these documents. See https://creativecommons.org/licenses/by/3.0/ for more details.

The following Google style guides live outside of this project: Go Code Review Comments and Effective Dart.