6f129c123e
This change updates docstrings and comments so that they will produce nicer formatting and cross-references from Sphinx. There are a few broad categories of changes: - Paramter and attribute docs are updated so that types will be recognized by Napoleon (https://sphinxcontrib-napoleon.readthedocs.io/en/latest/) This usually just means moving a colon in the docstring, so `name: (type) description` becomes `name (type): description`. - References to other symbols can be cross-references if they have the right format. For example, "attr_name" might become ":attr:`attr_name`". https://www.sphinx-doc.org/en/master/usage/restructuredtext/domains.html#cross-referencing-python-objects - For fenced code blocks, adding a double-colon `::` signifies a literal block. https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#literal-blocks - Some bits of docstrings move from docstring to comments. For TODOs, this means we won't be putting stale (or otherwise unrelated) noise into the docs. For `Message.DESCRIPTOR`, the change means it gets appropriate documentation. - There are some wording tweaks for consistency, and some new docstrings (especially for methods in Message). For types, I used the convention of `list[Foo]` and `dict(foo, bar)`, which seem to be common among other Python rst docstrings. Sphinx should generally recognize both, and cross-links them correctly (both internally and to Python library documentation). Upgrading to Python3-style type annotations would allow us to use `sphinx-autodoc-typehints`; the changes in this commit are very similar to typing-based hints. |
||
|---|---|---|
| .github | ||
| benchmarks | ||
| cmake | ||
| conformance | ||
| csharp | ||
| docs | ||
| editors | ||
| examples | ||
| java | ||
| js | ||
| kokoro | ||
| m4 | ||
| objectivec | ||
| php | ||
| protoc-artifacts | ||
| python | ||
| ruby | ||
| src | ||
| third_party | ||
| util/python | ||
| .bazelignore | ||
| .gitignore | ||
| .gitmodules | ||
| .readthedocs.yml | ||
| appveyor.bat | ||
| appveyor.yml | ||
| autogen.sh | ||
| BUILD | ||
| build_files_updated_unittest.sh | ||
| cc_proto_blacklist_test.bzl | ||
| CHANGES.txt | ||
| compiler_config_setting.bzl | ||
| composer.json | ||
| configure.ac | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS.txt | ||
| generate_changelog.py | ||
| generate_descriptor_proto.sh | ||
| global.json | ||
| LICENSE | ||
| Makefile.am | ||
| post_process_dist.sh | ||
| protobuf_deps.bzl | ||
| Protobuf-C++.podspec | ||
| protobuf-lite.pc.in | ||
| protobuf.bzl | ||
| protobuf.pc.in | ||
| Protobuf.podspec | ||
| README.md | ||
| tests.sh | ||
| update_compatibility_version.py | ||
| update_file_lists.sh | ||
| update_version.py | ||
| WORKSPACE | ||
Protocol Buffers - Google's data interchange format
Copyright 2008 Google Inc.
https://developers.google.com/protocol-buffers/
Overview
Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can find protobuf's documentation on the Google Developers site.
This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.
Protocol Compiler Installation
The protocol compiler is written in C++. If you are using C++, please follow the C++ Installation Instructions to install protoc along with the C++ runtime.
For non-C++ users, the simplest way to install the protocol compiler is to download a pre-built binary from our release page:
https://github.com/protocolbuffers/protobuf/releases
In the downloads section of each release, you can find pre-built binaries in zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary as well as a set of standard .proto files distributed along with protobuf.
If you are looking for an old version that is not available in the release page, check out the maven repo here:
https://repo1.maven.org/maven2/com/google/protobuf/protoc/
These pre-built binaries are only provided for released versions. If you want to use the github master version at HEAD, or you need to modify protobuf code, or you are using C++, it's recommended to build your own protoc binary from source.
If you would like to build protoc binary from source, see the C++ Installation Instructions.
Protobuf Runtime Installation
Protobuf supports several different programming languages. For each programming language, you can find instructions in the corresponding source directory about how to install protobuf runtime for that specific language:
| Language | Source | Ubuntu | MacOS | Windows |
|---|---|---|---|---|
| C++ (include C++ runtime and protoc) | src |    |
  |
|
| Java | java |     |
||
| Python | python |               |
   |
 |
| Objective-C | objectivec |     |
||
| C# | csharp |  |
 |
|
| JavaScript | js |  |
 |
|
| Ruby | ruby |      |
     |
|
| Go | golang/protobuf | |||
| PHP | php |   |
  |
|
| Dart | dart-lang/protobuf |  |
Quick Start
The best way to learn how to use protobuf is to follow the tutorials in our developer guide:
https://developers.google.com/protocol-buffers/docs/tutorials
If you want to learn from code examples, take a look at the examples in the examples directory.
Documentation
The complete documentation for Protocol Buffers is available via the web at: