On Mon, Jul 20, 2009 at 09:19:10PM -0700, Yingjie Lan wrote:

This is to announce the initial release of expy 0.1.0. More details at http://expy.sourceforge.net/

What is it (the announcement is too brief and I'm not going to click on a link without a real need)? How does it help core developers to develop Python (if you posted this to the python-dev mailing list instead of c.l.p or c.l.p.a)? Oleg. -- Oleg Broytmann http://phd.pp.ru/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.

--- On Sat, 8/8/09, Stefan Behnel wrote:

From: Stefan Behnel Subject: Re: [Python-Dev] expy: an expressway to extend Python To: python-dev@python.org Date: Saturday, August 8, 2009, 4:55 PM

...

More details at http://expy.sourceforge.net/

I'm clearly biased, but my main concern here is that expy requires C code to be written inside of strings. There isn't any good editor support for that, so I doubt that expy is good for anything but very thin wrappers (as in the examples you presented).

Thanks a lot for the input -- I sort of recaptured the advantages of expy and listed four points in the new introduction at http://expy.sf.net/ homepage. Lacking of editor highlight support is quite a problem, but it is possible to create a support. For example, you can use this to indicate the start of embedded code highlight: return """ and then the end mark is of course the enclosing """

That said, you might want to look at the argument unpacking code generated by Cython. It's highly optimised through specialisation and has been benchmarked quite a bit faster than the generic Python C-API functions for tuple/keyword extracting. Since argument conversion seems to be more or less all that expy really does, maybe you want to reuse that code.

Stefan

Oh sure, that's nice if that part can be adopted by expy-cxpy. Any help out on this would be very welcomed. Yingjie