Open GoogleCodeExporter opened 8 years ago
Yes, I think that is the right approach. In fact, I've been tentatively
planning to
use protobufs for the next version of this library to mirror the work on
java-twitter. The python protobuf interface does exactly what you recommend.
See
http://code.google.com/apis/protocolbuffers/docs/reference/python-generated.html
for
details.
This will of course break backward compatibility, so it should wait until a
version 2.0.
Original comment by dclinton
on 2 Mar 2009 at 5:38
I'm a big +1 on this too. If class members have well-chosen names, they don't
even
need commenting (they can be described in the docs, in examples, of course), let
alone a getter/setter. The above example is nicely chosen :-)
Terry
Original comment by terry.jo...@gmail.com
on 2 Mar 2009 at 5:45
Original issue reported on code.google.com by
spa...@gmail.com
on 2 Mar 2009 at 5:27