| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
* A few more cases for binary conformance tests.
* over-encoded varints (encoded in more bytes than are necessary).
* truncated varints (>32 bits for 32-bit types).
* Fixed Python decoding bug with 32-bit varints.
* Fixed 1L -> 1LL for 32-bit platforms.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#1971)
* Factored Conformance test messages into shared test schema.
* Updated benchmarks to use new proto3 message locations.
* Fixed include path.
* Conformance: fixed include of Python test messages.
* Make maven in Rakefile use --batch-mode.
* Revert changes to benchmarks.
On second thought I think a separate schema for
CPU benchmarking makes sense.
* Try regenerating C# protos for new test protos.
* Removed benchmark messages from test proto.
* Added Jon Skeet's fixes for C#.
* Removed duplicate/old test messages C# file.
* C# fixes for test schema move.
* Fixed C# to use the correct TestAllTypes message.
* Fixes for Objective C test schema move.
* Added missing EXTRA_DIST file.
|
|
|
|
|
| |
In Python 3 the values() method on a dictionary returns a view instead
of a list, so we need to explicitly convert that to a list.
|
|
|
|
|
| |
The curly brace syntax for sets was introduced in Python 2.7, and so for
compatibility with 2.6 we need to avoid using it for now.
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
the extension doesn't require installing protobuf library. (#2232)
|
| |
|
|
|
|
|
|
| |
[skip ci]
Change-Id: I1ba6f6372a08b5796570851336e1a548602f60da
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Fix to typo/oversight in python tests, only affecting python 3
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
In Python 2.6 the positional argument specifiers are apparently required
to be explicitly specified:
http://stackoverflow.com/questions/10054122/valueerror-zero-length-field-name-in-format-python
|
|
|
|
| |
This includes all internal changes from around May 20 to now.
|
| |
|
|
|
|
|
| |
OS X's version of Python has a slightly different error
message for this error case.
|
| |
|
| |
|
|
|
|
|
| |
Python 2.x doesn't detect unpaired surrogates so we have to
do that manually.
|
|\
| |
| | |
Merge beta-3 release branch again.
|
| |
| |
| |
| | |
of {}
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\| |
|
| | |
|
| |\
| | |
| | | |
Update version to 3.0.0b2.post2
|
| |/
|/| |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Improves #1296.
The problem: in the previous patch, we tweaked the __init__.py files to use
namespaces, but no longer declared ourselves as a namespace package. The
second half was unwise.
Note that this only comes up when installing protobuf alongside another
package that also installs into the google namespace; as of right now, the
only PyPI package that does is googleapis-common-protos, though the GAE SDK
also uses google.appengine. Installing either or both of those alongside this
package now works.
The case that still remains is the upgrade path, which is also what worried me
in #713. It seems that if protobuf 2.6.1 is installed, there's no way to
safely upgrade that to work with a newer protobuf. However, `pip uninstall` &&
`pip install` does the trick.
|
| |
|