| commit | 36ecf16f770ce2faaa49cf488c427968a7b29631 | [log] [tgz] |
|---|---|---|
| author | Jon Brandvein <brandjon@google.com> | Mon Jan 02 18:43:42 2017 +0000 |
| committer | John Cater <jcater@google.com> | Tue Jan 03 15:04:36 2017 +0000 |
| tree | ca6de66434e25547891d426b67d9879612887165 | |
| parent | d810d9ad51aca1d8b7e74406cb80943791f90547 [diff] |
Make the string strip() methods compatible with Python strip(), lstrip(), and rstrip() now accept a None argument as a synonym for the no-arg version. The characters that are considered as whitespace (to be removed by default in the no-arg form) are now the same as in Python 3.6. RELNOTES[INC]: The string methods strip(), lstrip(), and rstrip() now by default remove the same whitespace characters as Python 3 does, and accept None as an argument. -- PiperOrigin-RevId: 143388250 MOS_MIGRATED_REVID=143388250
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.