Well, my detailed plan for now is to look at Doug's implementation on the
Java side and mimic it. Once I get it working, I'll remove the Java-isms and
make it more Pythonic.
Creating classes and dynamically adding properties seems like how things
will work; it's going to be a bit "magical". If you want to sketch out your
implementation direction further, or even get a little code down, I'll be
happy to spend a bit more time on my critique.
On Mon, Aug 2, 2010 at 11:11 AM, Esteve Fernandez <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 20, 2010 at 12:26 AM, Jeff Hammerbacher <[EMAIL PROTECTED]>
> > I've added AVRO-588 (Avro usable and testable on Python 2.4). I'll need
> > augment the Python RPC to handle system errors correctly after AVRO-573
> > in, so I've filed AVRO-599 as a blocker as well. Lastly, I've been
> > to get to AVRO-528 (Twisted support) and AVRO-283 (change Python
> > implementation from dictionaries to objects) forever, so the release
> > as good as ever.
> I'd love to see AVRO-283, actually I started putting together a patch
> a while ago, but I thought it was too "magical" and wouldn't get as
> chance of getting accepted, as it created classes on the fly and so
> How did you plan to implement it? I'd be very happy to help if I can.