I don't know much about Python. Petar, do you know?
On Mon, Apr 27, 2009 at 10:09 AM, Yegor <yegor.jba...@gmail.com> wrote:
> Hi, Kenton,
> In the Python version there are now two versions of InputStream, one
> buffer-based, the other one array-based, for compatibility with App
> Engine-like environments. Do you know how big the performance penalty
> is for using array-based InputStream in protobuf context?
> On Apr 24, 9:01 pm, Kenton Varda <ken...@google.com> wrote:
> > Hi all,
> > I just updated SVN (rev 120) with a large bundle of changes recently made
> > our internal copy of the code. The easiest way to see what's new is to
> > at the diff of CHANGES.txt:
> > http://code.google.com/p/protobuf/source/diff?spec=svn120&r=120&forma...
> > Most of the changes probably won't affect most users (aside from
> > optimizations which silently affect you).
> > There are a couple obscure source-incompatible changes. For example,
> > UnknownFieldSet has been redesigned for efficiency, and its interface has
> > changed as a result. Most users do not use UnknownFieldSet directly, so
> > this is unlikely to affect many people, but if you do, then you'll need
> > update your code. Sorry -- the previous design of UnknownFieldSet was
> > really poor, and we saw no way around changing the API here.
> > The next release of protocol buffers will be version 2.1.0, possibly with
> > the "beta" tag like 2.0.0 had. Given all the changes, I imagine a few
> > have been introduced somewhere in there. I hope to get a release
> > out next week, followed by a real release shortly after.
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to
For more options, visit this group at