From: Samuele P. <ped...@op...> - 2007-12-28 20:44:23
|
Charlie Groves wrote: > I'm planning on merging the exposed_annotation branch to trunk this > weekend. It allows types written in Java to be exposed to Python > using annotations on the methods and fields to be made visible rather > than with the *exposed templates in src/templates. I've written up > the basics for using it at > http://wiki.python.org/jython/PythonTypesInJava I figured it was > worth bringing up since it changes how the core classes are > represented, and could cause some slight breakage that I'm missing. I > merged from trunk to it a couple days ago and all of regrtest passes, > so if it is broken, it's not broken terribly. > > I'd like to merge it fairly soon to allow new types being written > using this system rather than forcing new developers to learn the > templating system. I'd also like to set up some Google Highly Open > Participation tasks to convert the remaining classes to the > annotations: I've only converted PyBuiltinFunction, PyInteger, PyNone, > PyObject, PyString, PyType and PyUnicode. I've already got a couple > other GHOP tasks available for students to take, and I'd like to put a > couple more up and this seems like an ideal candidate. The > implementation has reached a point where it can do everything the > templates can, so now seems like a good time. > > I would say go ahead, although as I feared the with the new code is more cryptic to know what the generated code does, it is very positively less code than the old approach and doesn't involve maintaining a full obscure Java parser and is using techniques that should be more familiar and documented for Java programmers. Merging is probably the best way to hammer out the last problems. Samuele |