[IronPython] What's the situation on being able to accept patches?

Dan Eloff dan.eloff at gmail.com
Mon Oct 13 09:52:48 PDT 2008

I've completed the _ast module, fully implementing all classes from
the CPython module for Python 2.5. In the end the only way to do it
was as a patch to IronPython, partly because creating an ast from
source is done through the compile() builtin, but also because someone
did an optimization on GeneratorExpression that gave no public
interface to the syntax info. I patched GeneratorExpression to provide
the same public interface as ListComprehension, while making sure not
to affect the optimization. So now you have a 2500 lines of code patch
for IronPython that you cannot yet accept. What's the situation here?
How long is this likely to remain a problem (with the answer so
dependent on lawyers I'm not optimisitc)

It's way too late for this to end up in 2.0, but I was hoping for 2.1.

And if I supply a python doctest with the patch is that even useful to
you guys in your testing harness?


More information about the Users mailing list