README.txt 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. Protocol Buffers - Google's data interchange format
  2. Copyright 2008 Google Inc.
  3. This directory contains the Python Protocol Buffers runtime library.
  4. Normally, this directory comes as part of the protobuf package, available
  5. from:
  6. https://developers.google.com/protocol-buffers/
  7. The complete package includes the C++ source code, which includes the
  8. Protocol Compiler (protoc). If you downloaded this package from PyPI
  9. or some other Python-specific source, you may have received only the
  10. Python part of the code. In this case, you will need to obtain the
  11. Protocol Compiler from some other source before you can use this
  12. package.
  13. Development Warning
  14. ===================
  15. The Python implementation of Protocol Buffers is not as mature as the C++
  16. and Java implementations. It may be more buggy, and it is known to be
  17. pretty slow at this time. If you would like to help fix these issues,
  18. join the Protocol Buffers discussion list and let us know!
  19. Installation
  20. ============
  21. 1) Make sure you have Python 2.6 or newer. If in doubt, run:
  22. $ python -V
  23. 2) If you do not have setuptools installed, note that it will be
  24. downloaded and installed automatically as soon as you run setup.py.
  25. If you would rather install it manually, you may do so by following
  26. the instructions on this page:
  27. https://packaging.python.org/en/latest/installing.html#setup-for-installing-packages
  28. 3) Build the C++ code, or install a binary distribution of protoc. If
  29. you install a binary distribution, make sure that it is the same
  30. version as this package. If in doubt, run:
  31. $ protoc --version
  32. 4) Build and run the tests:
  33. $ python setup.py build
  34. $ python setup.py google_test
  35. If you want to build/test c++ implementation, run:
  36. $ python setup.py build --cpp_implementation
  37. $ python setup.py google_test --cpp_implementation
  38. If some tests fail, this library may not work correctly on your
  39. system. Continue at your own risk.
  40. Please note that there is a known problem with some versions of
  41. Python on Cygwin which causes the tests to fail after printing the
  42. error: "sem_init: Resource temporarily unavailable". This appears
  43. to be a bug either in Cygwin or in Python:
  44. http://www.cygwin.com/ml/cygwin/2005-07/msg01378.html
  45. We do not know if or when it might me fixed. We also do not know
  46. how likely it is that this bug will affect users in practice.
  47. 5) Install:
  48. $ python setup.py install
  49. or:
  50. $ python setup.py install --cpp_implementation
  51. This step may require superuser privileges.
  52. NOTE: To use C++ implementation, you need to install C++ protobuf runtime
  53. library of the same version and export the environment variable before this
  54. step. See the "C++ Implementation" section below for more details.
  55. Usage
  56. =====
  57. The complete documentation for Protocol Buffers is available via the
  58. web at:
  59. https://developers.google.com/protocol-buffers/
  60. C++ Implementation
  61. ==================
  62. The C++ implementation for Python messages is built as a Python extension to
  63. improve the overall protobuf Python performance.
  64. To use the C++ implementation, you need to:
  65. 1) Install the C++ protobuf runtime library, please see instructions in the
  66. parent directory.
  67. 2) Export an environment variable:
  68. $ export PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp
  69. $ export PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION_VERSION=2
  70. You need to export this variable before running setup.py script to build and
  71. install the extension. You must also set the variable at runtime, otherwise
  72. the pure-Python implementation will be used. In a future release, we will
  73. change the default so that C++ implementation is used whenever it is available.
  74. It is strongly recommended to run `python setup.py test` after setting the
  75. variable to "cpp", so the tests will be against C++ implemented Python
  76. messages.