7f3e237071
* Down-integrate internal changes to github.
* Update conformance test failure list.
* Explicitly import used class in nano test to avoid random test fail.
* Update _GNUC_VER to use the correct implementation of atomic operation
on Mac.
* maps_test.js: check whether Symbol is defined before using it (#2524)
Symbol is not yet available on older versions of Node.js and so this
test fails with them. This change just directly checks whether Symbol is
available before we try to use it.
* Added well_known_types_embed.cc to CLEANFILES so that it gets cleaned up
* Updated Makefile.am to fix out-of-tree builds
* Added Bazel genrule for generating well_known_types_embed.cc
In pull request #2517 I made this change for the CMake and autotools
builds but forgot to do it for the Bazel build.
* Update _GNUC_VER to use the correct implementation of atomic operation on Mac.
* Add new js file in extra dist.
* Bump version number to 3.2.0
* Fixed issue with autoloading - Invalid paths (#2538)
* PHP fix int64 decoding (#2516)
* fix int64 decoding
* fix int64 decoding + tests
* Fix int64 decoding on 32-bit machines.
* Fix warning in compiler/js/embed.cc
embed.cc: In function ‘std::string CEscape(const string&)’:
embed.cc:51:32: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < str.size(); ++i) {
^
* Fix include in auto-generated well_known_types_embed.cc
Restore include style fix (
|
||
|---|---|---|
| .. | ||
| compatibility_tests/v2.5.0 | ||
| MANIFEST.in | ||
| mox.py | ||
| README.md | ||
| setup.cfg | ||
| setup.py | ||
| stubout.py | ||
| tox.ini | ||
Protocol Buffers - Google's data interchange format
Copyright 2008 Google Inc.
This directory contains the Python Protocol Buffers runtime library.
Normally, this directory comes as part of the protobuf package, available from:
https://developers.google.com/protocol-buffers/
The complete package includes the C++ source code, which includes the Protocol Compiler (protoc). If you downloaded this package from PyPI or some other Python-specific source, you may have received only the Python part of the code. In this case, you will need to obtain the Protocol Compiler from some other source before you can use this package.
Development Warning
The Python implementation of Protocol Buffers is not as mature as the C++ and Java implementations. It may be more buggy, and it is known to be pretty slow at this time. If you would like to help fix these issues, join the Protocol Buffers discussion list and let us know!
Installation
-
Make sure you have Python 2.6 or newer. If in doubt, run:
$ python -V
-
If you do not have setuptools installed, note that it will be downloaded and installed automatically as soon as you run setup.py. If you would rather install it manually, you may do so by following the instructions on this page:
https://packaging.python.org/en/latest/installing.html#setup-for-installing-packages
-
Build the C++ code, or install a binary distribution of protoc. If you install a binary distribution, make sure that it is the same version as this package. If in doubt, run:
$ protoc --version
-
Build and run the tests:
$ python setup.py build $ python setup.py test
To build, test, and use the C++ implementation, you must first compile libprotobuf.so:
$ (cd .. && make)
On OS X:
If you are running a homebrew-provided python, you must make sure another version of protobuf is not already installed, as homebrew's python will search /usr/local/lib for libprotobuf.so before it searches ../src/.libs You can either unlink homebrew's protobuf or install the libprotobuf you built earlier:
$ brew unlink protobuf or $ (cd .. && make install)
On other *nix:
You must make libprotobuf.so dynamically available. You can either install libprotobuf you built earlier, or set LD_LIBRARY_PATH:
$ export LD_LIBRARY_PATH=../src/.libs or $ (cd .. && make install)
To build the C++ implementation run: $ python setup.py build --cpp_implementation
Then run the tests like so: $ python setup.py test --cpp_implementation
If some tests fail, this library may not work correctly on your system. Continue at your own risk.
Please note that there is a known problem with some versions of Python on Cygwin which causes the tests to fail after printing the error: "sem_init: Resource temporarily unavailable". This appears to be a bug either in Cygwin or in Python: http://www.cygwin.com/ml/cygwin/2005-07/msg01378.html We do not know if or when it might be fixed. We also do not know how likely it is that this bug will affect users in practice.
-
Install:
$ python setup.py install
or:
$ (cd .. && make install)
$ python setup.py install --cpp_implementation
This step may require superuser privileges. NOTE: To use C++ implementation, you need to export an environment variable before running your program. See the "C++ Implementation" section below for more details.
Usage
The complete documentation for Protocol Buffers is available via the web at:
https://developers.google.com/protocol-buffers/
C++ Implementation
The C++ implementation for Python messages is built as a Python extension to improve the overall protobuf Python performance.
To use the C++ implementation, you need to install the C++ protobuf runtime library, please see instructions in the parent directory.